Use URL Inspection to find whether Google can access the page and whether a different canonical URL explains the report. Start by investigating a useful URL stays out of search after launch. Ask the web developer to own the first review and use URL Inspection results and deployment log to establish what should happen. This gives the team a clear reference when a customer sees something different or a report seems to tell a different story.
When reviewing URL Inspection, distinguish the live URL test from Google's last indexed view. A successful live fetch tells you something about current access. Google may still select a different canonical or take time to recrawl. Use an affected page and a working peer from the same template to isolate the difference.
Walk through a real customer scenario
Consider this example. A published service page works in a browser but the site points its canonical at an old URL. A blog URL canonicalized to a different article can disappear from search even when it loads normally. Verify which page should be the canonical destination. Start the test at the same point a customer would, using the device or channel they normally use. Record what you expected at each handoff and what the customer actually received. Keep the first failed step in the notes so another person can repeat the test.
Run a second test that could reveal whether the issue is isolated. Pick a similar page, location, product or audience that should work under the same conditions. An exception worth recording is that the live test passes but the indexed version still reflects an older crawl. Write down when you tested, which account or browser you used if relevant, and whether the result can be reproduced with a fresh visit. If it occurs only once, leave the case open until the web developer can check it again.
For related work, see our SEO services. Review the parts that affect this journey before choosing what to change.
Follow the workflow
- Inspect the affected URL.
Before making an edit, capture the current state. Use URL Inspection results and deployment log as the reference and write down the exact URL, item, audience or date you checked. If two records disagree, ask the web developer which one should determine the public or operational result. Keep both versions in the work record until you know why they differ.
- Compare indexed and live information.
Describe the customer action in plain language and record the point where it stops matching your expectation. In this review, you are looking for a useful URL stays out of search after launch. Include any handoff to a booking system, payment provider, report or person. A screenshot is useful when it shows what was on screen, but record the action that produced it as well.
- Check status, canonical and page directives.
Apply the first change to a representative case. Check response, directives, canonical and internal links together. Record the implementation date and the person who made the change. If several components are connected, test the downstream step before repeating the change elsewhere. For a live promotion or a busy booking period, agree who can revert the change if the test fails.
- Fix the root issue and validate related URLs.
Repeat the first walkthrough and verify the last step with the team that receives the result. Ask the web developer to check a second example if the same setup is used elsewhere. Where there is a receipt, booking confirmation, order record or data export, compare it with what the customer saw before closing the issue.
Decide which issue to fix first
Prioritise the first defect that prevents the customer from completing the task. Check whether staff resubmit the same URL without addressing the reason in the report. If the evidence points to a particular page, rule or handoff, make the smallest change that addresses it. When the evidence is unclear, assign a focused test before requesting a larger rewrite or technical change.
Give the web developer a short handover with the affected item, the expected result, the observed result and a recheck date. Name the person who can implement the fix. Add the original export or test record so the reviewer can inspect the evidence directly. For work involving more than one team, agree who is responsible for checking the complete customer experience once the pieces are in place.
When the change requires additional implementation, see our technical SEO audits for the work this review can inform.
Measure the result after the change
Use important pages indexed and crawl errors resolved to judge the outcome. Define the measure before comparing results so everyone uses the same starting and ending points. Match the period, audience, location or product selection as closely as practical. Keep a dated note of changes in staffing, offers, inventory or tracking that could affect the comparison.
Your first follow-up should be to verify the affected template and record the date you expect a meaningful recheck. Add the correct URL to the sitemap and link to it from a relevant indexed page. Recheck after recrawl. If the workflow now passes but the business result stays flat, inspect the next customer action. A website can correctly accept a request while the team that receives it takes too long to respond. Similarly, an event can be recorded accurately while failing to represent the outcome the team cares about.
Write down the raw counts alongside any rate, especially if the review covers a small number of visits or orders. Record what changed, what customers can now do and what still needs work. When there is too little evidence to make a decision, leave the current setup in place while the web developer schedules a comparable follow-up.
Test one other page that uses the same template before calling the fix complete. Shared navigation, headings, images, scripts and page settings can affect more URLs than the one that first exposed the problem. Record which pages share the implementation and which require their own changes.
Frequently asked questions
Where should I start with indexing investigation?
Inspect the affected URL. Pick an example with clear evidence and walk through it from the customer's starting point. Document what must happen for the test to pass, then ask another person to repeat it with the same inputs.
When should I check the results?
Recheck the customer-facing change as soon as it is live. Give important pages indexed and crawl errors resolved a comparable period to collect data and check whether anything else changed during that period. If the functional check fails, reopen the original work item and add the new evidence before testing a broader change.
Reference Source documentation.
For help putting the plan into practice, book a strategy call.
