Check access and page responses
Sample important page types and review status codes, crawl controls and initial content. Identify whether the intended page is available at the expected URL. Keep raw-response findings separate from what a rendered browser or Search Console shows.
Crawl findings and technical priorities
Inspect crawl status, indexability and page-level findings before prioritising fixes.
Review signals together
Compare canonical URLs, internal links and sitemap entries. Inspect the title, main heading and content for representative templates. An issue affecting every service page usually needs a template fix rather than dozens of isolated edits.
Turn findings into work
For each priority item, record affected URLs, evidence, business impact, owner and an acceptance check. Separate immediate defects from improvements that need more evidence. Retest changed templates and preserve the record of what was fixed.
Put the guidance to work
Capture your starting point, assign an owner to the next action, and decide what evidence will confirm that it worked.
Discuss this with us