Check whether important pages require login or cookies to load

Written by

in

Open the homepage and representative content pages in a private browser where you are not logged in. Test whether menus, article text, images, and forms load. Google’s approval guidance notes pages behind login or restricted access among potential navigation problems. If public content is intended for visitors, make sure it is actually public; if a page is intentionally private, do not treat it as a public landing page.

Consent tools can also affect what loads before a visitor makes a choice. Check that the banner does not create an empty page or block basic navigation, while still honoring applicable consent requirements. Test both first visit and returning visit states.

Use SiteReadyScore from a public perspective to find pages that may need access checks. It cannot test all account roles or private content states, so verify with a logged-out browser and the site’s own test accounts.

Related guides