Connect Search Console and check your important pages

Choose the property that covers your website

Google's Domain property covers protocols and subdomains and generally uses DNS verification. A URL-prefix property covers only the specified prefix, including its protocol, and offers several verification methods. Choose deliberately so you do not mistake an empty report for an empty website.

Keep ownership with the business

Our recommended setup uses a business-controlled Google account for ownership and grants appropriate access to any helper. Keep the domain registrar and website credentials in the business's own records. A supplier leaving should not prevent you from seeing your website's search information.

For a Domain property, follow Search Console's exact DNS instructions through the provider that actually hosts your DNS. Do not replace existing email or website records. If you are unsure where records are managed, ask the domain administrator to add the verification record. For a URL-prefix property, use the verification method your platform supports and retain the required token or file.

Inspect two URLs before reading every chart

Paste the full homepage URL into the inspection bar, then repeat with your most important service page. URL Inspection shows stored information about Google's indexed version; its live test checks the current page's potential indexability. A successful live test does not prove that the page is indexed or will appear in results.

Write down the result and the next action

Use a simple log with URL, intended purpose, indexed status, live-test result, issue, owner, and action date. If the homepage is indexed but a new service page is not, investigate that page rather than treating the whole domain as broken. If the reported canonical is unexpected, share the exact pair of URLs with your developer.

For a reported access problem, ask whether the page is published, available without login, and using the intended live hostname. For an indexing restriction, check whether a staging setting was left on. Keep the original report or a screenshot so the person fixing the issue can compare the same evidence afterward.

Request indexing after a meaningful fix

Google allows eligible property users to request indexing for individual URLs, but repeated requests do not accelerate crawling and inclusion is not guaranteed. Use the request after publishing or resolving a real issue rather than as a daily ritual.

Build a manageable review routine

Start with the pages that matter to customer acquisition: the homepage, primary services, contact information, and a few valuable guides. A tiny site does not need an elaborate reporting dashboard on day one. Review unresolved issues after the fix has been deployed and keep a record of what changed.

When delegating, ask for a short explanation in plain language: which customer-facing page is affected, what caused the issue, what was changed, and how the live page was checked. That creates a useful handover instead of a folder of unexplained screenshots. Search Console becomes valuable when its observations lead to a specific, verified website improvement.