- Check eligibility
- Compare intent
- Inspect evidence
Can the page be found and understood?
Confirm the page is available, linked from the site and intended for indexing. Use Search Console evidence where access is available. Distinguish an indexing problem from a page that is indexed but receives little relevant visibility.
Does it answer the right question?
Compare the page's purpose with what the searcher is trying to accomplish. Look for missing scope details, unsupported claims and redundant pages. Do not assume a penalty from a single traffic drop. Dappr can investigate technical and editorial causes together, then prioritize changes according to evidence rather than publish more pages automatically.
Define what “not ranking” means before changing the site
Start with the exact observation. Is a specific page absent from the index, appearing for unexpected queries, receiving fewer clicks or failing to produce inquiries? These are different problems. Write down the affected URL, the query or report, the date range and what changed. A diagnosis becomes much more useful when it refers to something another person can inspect.
Avoid using one personal search as the entire performance record. The result you see is an observation in a particular context, not a complete account of the site’s visibility. Where account access is available, use relevant Search Console evidence and retain the filters and period used. Separate a branded search from a broader service query because the business questions are different.
A fictional service company might say its website has disappeared when its homepage still appears for the business name but a service page receives few relevant impressions. Another might discover that a recently launched page is not intended for indexing at all. The same phrase describes two investigations, and neither should begin with an automatic order for more articles.
Inspect the affected page and its intended status
Open the exact address and follow the customer path that leads to it. Check whether it returns the expected page, redirects somewhere else or fails. Compare the visible content with the page the business intended to publish. A correct-looking homepage does not establish that every service page or alternate address works.
Have the site owner or developer inspect indexing controls and the preferred URL configuration. Preview pages may deliberately be excluded from search, while a production page may have inherited an unintended restriction. Record the actual setting and its purpose before changing it. Removing every restriction without understanding the environment can expose material that was never intended to be public.
Check whether the page can be found through relevant links within the site. If the only way to reach it is a private review link, the discovery path may be incomplete. Then compare the current page with available search inspection information. Do not assume that a live browser test and previously recorded crawler information represent the same moment.
Look for a mismatch between the page and the reader’s task
Describe the query as a task in ordinary language. Is the reader choosing a provider, learning a process, comparing approaches or looking for a specific business? Then describe what the page actually provides. A sales page with a vague offer may not satisfy a detailed educational question, while a long article may make a ready buyer search elsewhere for service information.
Review the results relevant to the intended audience and note the kinds of answers available. Use this as evidence about the question, not an instruction to copy competitors. Look for information your business can provide accurately: scope boundaries, preparation requirements, decision criteria or a clear explanation of how an inquiry is handled.
Check the title and introduction against the substance of the page. A title can promise a comparison while the body describes only one option. A local heading can imply an office that does not exist. Correcting those mismatches improves the honesty and usefulness of the page regardless of whether it changes a particular search position.
Review site changes and measurement changes separately
Create a timeline of meaningful events: a redesign, URL changes, revised navigation, deleted content, new indexing controls or changes to analytics. Compare the timing with the observed issue. A tracking interruption can reduce recorded visits without proving that fewer people arrived. A site move can affect specific paths even when overall traffic appears stable.
Ask for the smallest useful evidence set first. An affected URL, a before-and-after example and a dated deployment note may be more helpful than exporting every available report. If several pages share a template, investigate whether one implementation issue explains the pattern. This avoids rewriting individual pages when the problem belongs to the shared layout or routing.
Do not label a traffic change a penalty without evidence. If the owner has Search Console access, account notices and relevant reports can help narrow the investigation. If access is unavailable, document that limitation. A public-site review can identify visible issues but cannot certify the absence of account-level notices or reconstruct private historical data.
Prioritize a repair that can be verified
Turn the strongest finding into a specific change. An unintended redirect needs a correct destination; an unclear service page needs accurate scope; a broken inquiry route needs a working handoff. Define what passing looks like before implementation. This prevents the investigation from expanding into an unrelated redesign simply because many improvements are possible.
Separate implementation verification from search performance evaluation. A repaired link can be checked immediately. Whether the revised page gains useful visibility is a different observation that depends on later evidence. Report both stages honestly rather than claiming a ranking improvement from the fact that a deployment succeeded.
Preserve a record of what changed and why. If several changes are released together, acknowledge that attributing a later result to one edit may be difficult. When practical, group work around a coherent problem so the team can interpret the outcome. Avoid changing the target, content and measurement definition at every review.
Know when the investigation needs more information
Sometimes the site has no obvious access defect and the page answers a real question, yet visibility remains limited. That does not justify inventing a hidden cause. The next step may be better query research, an expert review of the content, a comparison of competing answers or more representative account evidence. State the unanswered question clearly.
A useful handoff includes the affected addresses, the observed behavior, the checks already completed and the remaining uncertainty. Include relevant screenshots or report exports only when they are safe to share. Exclude credentials and unnecessary customer information. This lets another specialist continue the investigation without repeating the same preliminary work.
Dappr can review the technical and editorial sides of a discovery problem together. The aim is to distinguish what is demonstrably broken, what needs stronger information and what remains a hypothesis. A responsible recommendation explains the evidence behind its priority and does not guarantee that a specific edit will deliver a specific Google position.
Record the next decision, not just the next task
End the investigation with a decision statement: what will be corrected, what evidence supports that choice and what observation will determine the following step. If the evidence is insufficient, identify the missing information and who can supply it. This makes an uncertain diagnosis actionable without turning uncertainty into a confident claim about Google or the business’s competitors.