Verify the right property
A Domain property can cover protocols and subdomains through DNS verification, while a URL-prefix property covers the specific prefix you add. Choose the property that matches how you want to monitor the site and keep access with an account the business controls.
If a redesign or migration changes the preferred domain variant, make sure the property you monitor still represents the live site.
- Confirm ownership is under the correct Google account.
- Keep the verification record in place after setup.
- Add collaborators with the least access they need.
Submit a clean sitemap
Your sitemap should list canonical, indexable URLs that you actually want discovered. It should not become a dump of every parameter, redirect, 404, staging page or duplicate technical variant.
Submitting the sitemap helps Google discover URLs and gives you a clearer reporting surface. It does not guarantee that every submitted URL will be indexed.
- Use absolute HTTPS URLs.
- Remove redirected and noindex pages from the sitemap.
- Keep the sitemap accessible without login.
Use URL Inspection as a diagnostic tool
Inspect a priority page when you need to understand whether Google knows the URL, which canonical it selected and whether the page is blocked from indexing. The live test can help distinguish the current deployed state from an older indexed state.
Requesting indexing can be useful after a meaningful fix, but repeatedly pressing the button is not a substitute for crawlable internal links and a stable sitemap.
- Inspect the homepage and a representative service page.
- Compare user-declared and Google-selected canonical URLs.
- Use the live test after fixing noindex, redirect or rendering problems.
Interpret indexing exclusions in context
Not every excluded URL is a problem. Redirected URLs, duplicates and deliberately noindexed pages can be correctly excluded. Focus on important canonical pages that you expect in search but which remain blocked or undiscovered.
When a page is crawled but not indexed, review whether it is substantially useful, internally linked and distinct from other content. Technical changes cannot make low-value duplicate content necessary to index.
- Separate expected exclusions from real problems.
- Fix sitewide template mistakes before individual URLs.
- Avoid generating large amounts of thin content just to create indexable pages.
Monitor after migrations and launches
After a site migration, compare old and new properties where applicable, confirm redirects, submit the new sitemap and monitor indexing and crawl errors. Search changes take time to settle because crawlers need to revisit URLs.
Keep redirect rules stable. Removing redirects too quickly can strand old links and bookmarks before crawlers fully process the move.
- Check key redirects manually.
- Watch indexed page trends rather than daily fluctuations.
- Keep internal links updated to the new canonical URLs.
Use performance reports for prioritization
The Performance report shows queries, pages, clicks and impressions. Use it to learn which existing pages already receive visibility and which query themes deserve better answers or internal links.
Treat query data as evidence, not a reason to stuff phrases into copy. A page can rank for wording that never appears exactly when the content clearly answers the topic.
- Group related queries by intent.
- Compare page performance before and after substantial changes.
- Protect pages that already perform well before rewriting them broadly.
Use the related free tools for diagnosis, or describe the specific website problem in the project form. Keep passwords out of the enquiry.
Discuss a focused project ↗