Imagine a small recipe site with a menu, 40 recipes, and an About page. The contact page exists, but the footer link points to an old URL. On desktop, the menu works; on mobile, the menu button opens but the Contact item is missing. A visitor who wants to ask about an ingredient correction cannot find the route.
The audit should record what was observed, not guess what Google’s reviewer saw. Record the starting URL, device, steps, expected destination, actual result, and date. Example: “From /roasted-beets/ on a 390-pixel mobile viewport, tap the menu icon, then Contact. The menu closes without navigation.” Check several page templates because navigation may differ between an article and a category archive.
The repair is to restore the current Contact destination in the footer and mobile menu, then test direct and menu-based access. Also inspect whether the contact page itself loads and clearly identifies the route to reach the site owner. Google’s AdSense readiness guide emphasizes clear, easy-to-use navigation. Its rejection guidance describes navigation issues such as broken links and pages that are difficult to use.
This example does not prove that a contact page is a guaranteed approval requirement or that fixing one link guarantees approval. It shows how to turn an observable visitor problem into a verifiable repair. After the change, repeat the same steps on the same device and check another representative template.
Use SiteReadyScore to help identify pages and navigation signals that may deserve inspection. Add the specific broken path to your repair log, fix it, and recheck. A useful case study reports both what changed and what remains unknown.