1. Check that important public pages open
Open your homepage and key service pages in a private browser window. They should display the intended content without asking for an account. Follow the links from the homepage to check that a visitor can reach them.
Give your developer the exact address of any error page. If the issue is intermittent, include the time and what you clicked. This makes the report easier to investigate than “the website is broken”.
2. Review search visibility instructions
Ask your developer to review robots.txt and any noindex instructions on important public pages. Robots.txt controls crawler access. Noindex tells a supporting search engine to exclude a page once it can read that instruction.
Check these settings after a launch or redesign. Public service pages and private account pages have different purposes, so review their visibility individually. Use Search Console’s page inspection to investigate Google's result for a particular address.
3. Check your sitemap and internal routes
A sitemap can list the public pages you want search engines to discover. Review whether it reflects the current website and submit it in your Search Console account. Keep your main service pages linked through the website too.
Follow the links customers use to reach service details, forms and booking pages. Repair confirmed missing destinations and investigate access restrictions or timeouts separately.
4. Review duplicate addresses
A page may appear at more than one address because of an old URL, a copied page or different URL variants. Ask your developer to review redirects and canonical tags together. A canonical tag identifies a preferred address for equivalent content.
If a service moved from an old address, check the old link still leads to the appropriate service. Record both addresses so your developer can review the route and preferred page.
5. Check page titles, descriptions and headings
Give each important page a descriptive title and clear main heading. Review repeated titles across unrelated services. Use section headings to organise the page, and write a description that matches what a visitor will find.
Run the free audit to identify missing or repeated page information across up to five pages. Ask whether repeated issues come from a shared page template so you can repair the cause efficiently.
6. Review images, sharing and structured data
Provide useful text alternatives for informative images. Check that sharing a page displays an appropriate title, description and image. Where structured data fits the content, validate it and make sure its details match the visible page.
For example, a service page should use accurate business details. Remove outdated information from both the page and its markup when those details change.
7. Test performance and the mobile journey
Open the page on a phone and check the text, navigation and contact form. Review performance separately using a browser performance tool or PageSpeed Insights. Give the person implementing changes the affected page and the specific problem you observed.
8. Verify each repair
Keep a dated task list and check the affected pages after changes. Confirm that old links reach the intended destination and that forms still work. Run another audit to review the HTML fixes, then use Search Console to assess search visibility over time.