PageProof’s HTML web proofing is the easiest and most accurate way to gather feedback on live or staging website URLs, and also zip files containing HTML content (such as banner ads, email templates and websites).
HTML proofing readiness
PageProof uses a proxy to put your HTML content through into the PageProof proofing screen. Your website will need to allow PageProof access to your content (including access to the imagery and fonts). This is easy to do and effective immediately with this checklist:
HTML proofing checklist
- HTTPS everything. Make sure all your web content is sitting on https. Check through all the URLs inside your site and make sure references to CSS and images etc are all https. Https is best practice for websites since Google changed their security status in Google Chrome (and with Firefox also following Google’s lead).
- Use relative URLs instead of absolute URLs. For example, to reference an image for your site, use /images/image1.png rather than https://our-site-name.com/images/image1.png
- Allow *.static.pageproof.com in your X-Frame options and CORS controls - especially access to any resources like images and fonts you may have hosted on your own servers. This allows PageProof to embed your site inside the proofing screen.
- Font access. If you are using fonts from a provider such as Adobe Typekit, FontAwesome Pro CDN and others – allow *.static.pageproof.com read access to those fonts.
- Resource access. Similar to the font access above, if you have any resources which has an access restriction, add *.static.pageproof.com (API, SDK, image servers etc)
Here is a screenshot of the allowed access in Adobe TypeKit:
Once you have gone through the checklist above, your website content can be reviewed and approved in PageProof with ease. If you have any questions, please reach out to the PageProof support team via the in-app chat on the dashboard.