What Search Console can and cannot tell you
Search Console reports how Google encounters a verified site, including sitemap processing, selected search performance data and reported indexing issues. It is not a manual indexing switch and does not guarantee traffic, a ranking or inclusion in results.
Before you submit anything
- Check that the final URL returns a successful response and is not an accidental redirect.
- Confirm that robots rules allow crawling and the page does not carry an unintended noindex.
- Use one consistent HTTPS, hostname and trailing-slash format.
- Make the canonical point to the page’s preferred, working URL.
1. Verify the correct property
Add a Domain property for the domain if you need coverage across protocols and subdomains. Search Console will show the DNS TXT record to add through your domain provider. A URL-prefix property covers only the exact prefix you enter and offers different verification methods. Keep the verification method active so ownership is not lost.
2. Submit the XML sitemap
- Open the verified property and select Sitemaps.
- Enter the sitemap path, for example
sitemap.xml, and submit it. - Return to the report to check whether Google could fetch it and how many URLs it discovered.
- Make sure the sitemap lists canonical, public pages that return a successful status—not redirects, 404s, private pages or blocked URLs.
A sitemap improves URL discovery; it does not certify that every listed page is useful or eligible for indexing. Keep internal links to important pages as well.
3. Inspect an individual URL
Paste the exact URL into URL Inspection. Review the reported Google-selected canonical and the last crawl information. If the page has changed, run a live test. When it is accessible and eligible, you can request indexing. Use requests selectively for a small number of important, updated URLs instead of submitting the same URL repeatedly.
4. A careful domain-move checklist: buntytech.online to buntytech.com
For a domain change, preserve the old domain and its Search Console property while the move is being processed. The destination should be the most relevant equivalent URL—not automatically the new homepage.
- Keep the old domain active and configure a permanent server-side redirect for each old URL that has a relevant replacement.
- Update internal links, canonical tags, structured data, navigation and XML sitemaps to the new domain.
- Verify both old and new domain properties in Search Console.
- After redirects are working, submit the Change of Address request for the old property when the tool is available and the move qualifies.
- Submit the new domain’s sitemap and monitor both properties for crawl, indexing and redirect errors.
- Keep redirects in place for the long term and update important external links where you control them.
Google’s migration tools help communicate a move; they do not instantly transfer rankings or ensure every old URL is indexed on the new domain.
5. Interpret reports without guessing
“Discovered” and “crawled” are not the same as “indexed.” A duplicate page may be excluded because Google chose a different canonical. A blocked URL may not be fetched. A server error may prevent a crawl. Use the URL Inspection and Page Indexing details for the affected page, then compare the live response with your intended page behavior.
Need to troubleshoot a specific URL?
Use the free website audit for public technical signals, or contact BuntyTech with the URL and the exact Search Console status. The public audit cannot access private Search Console data.
Frequently asked questions
Does submitting a sitemap guarantee that Google will index every URL?
No. A sitemap helps Google discover canonical URLs, but Google decides whether and when to crawl and index each page. A submitted URL can remain excluded.
How do I verify my website in Search Console?
Add a Domain property for broad host coverage and follow the DNS TXT verification instructions shown by Search Console. A URL-prefix property has separate verification options. Keep the verification record in place.
How do I submit an XML sitemap?
Open the Sitemaps report for the verified property, enter the sitemap path such as sitemap.xml, and submit it. Check the report later for fetch status and discovered URLs.
How do I request indexing for one page?
Use URL Inspection on the exact canonical URL. If the live test shows it is accessible and eligible, select Request Indexing. This is a request, not a promise or a ranking signal.
Should I keep clicking Request Indexing?
No. Repeated requests do not make Google crawl a page faster. Fix the underlying issue, update the sitemap when appropriate and allow time for recrawling.
Why can a page remain unindexed?
Common causes include discovery or crawl problems, a noindex directive, robots restrictions, a different canonical, redirect or server errors, thin or duplicative value, and Google choosing not to index the page. Read the exact Search Console status.
How can I confirm whether Google indexed a URL?
Use URL Inspection in the correct verified property and review the Page Indexing report. A site: search is only a rough search result check and is not a complete indexing report.
What should I do when moving from buntytech.online to buntytech.com?
Keep the old domain available, redirect each old URL to its closest relevant new URL, update internal links and canonicals, submit the new sitemap, and use Search Console’s Change of Address tool when eligible. Monitor both properties during the move.
Should every old URL redirect to the homepage?
No. Redirect to a genuinely equivalent page when one exists. If content has permanently been removed and has no replacement, return an appropriate not-found or gone response rather than sending visitors to an unrelated page.
How long does indexing take after a request?
There is no fixed timeline. Google may crawl later, decline to index the URL or select another canonical. Keep the page useful, accessible and internally linked, then monitor the reported status.
