A website can load correctly while an alternate address is excluded from search. “Page with redirect” describes the address Google checked; it does not automatically mean the whole site is missing. First identify which URL you want considered and where the other versions lead.
Follow the address to its destination
In an illustrative setup, https://example.com/ redirects to https://www.example.com/. The first address is an alternate entry point; the www destination serves the actual homepage. If the redirect is intentional and correct, keep it. Trying to make both versions independently indexable can create conflicting duplication signals.
Inspect the destination separately in Search Console. A URL-prefix property for the non-www address does not cover the www hostname in the same way a verified domain property covers subdomains. Choose the property that actually includes the URL being inspected.
Distinguish a redirect status from a redirect error
A normal redirect points to a suitable final page. A loop, excessively long chain or invalid destination is a different problem. Open the intended destination, confirm its content and check the canonical signal. The message alone is not enough to prescribe deleting redirects.
Build a sitemap from intended final pages
Use a consistent preferred hostname, protocol and URL format. Include public canonical pages you want considered, not every tracking variation or obsolete redirect. For a small site, the sitemap generator can produce XML from a curated list. For a larger site, a publishing-system sitemap is easier to keep current.
Run the sitemap checker, then open a sample of the listed pages. XML structure and live page quality are separate checks. Only include accurate last-modified information when your publishing process can maintain it; a current date pasted onto unchanged content is not a useful update signal.
Check access without confusing the controls
Robots.txt directs crawling. It is not authentication and is not equivalent to a noindex instruction. Inspect any broad blocking rule in context, especially after moving from staging to production. Use the robots inspector as a prompt for review, then consult the search engine’s documentation for the relevant crawler behaviour.
Submit, inspect and interpret
Submit the accessible sitemap through the appropriate verified webmaster account. For an important page, inspect its exact final URL and read the reported state. If it is already indexed, an alternate address’s redirect exclusion may need no action. If it is not, use the stated reason to decide whether the issue is access, duplication, content or something else.
Google’s live test follows redirects, so distinguish the tested address from the final page it reaches. A successful live test establishes access at that time, not a promise of inclusion. Requesting indexing and submitting a sitemap are discovery actions; the search engine still decides whether and when to index a page.
Keep notifications in perspective
The IndexNow helper prepares ownership verification and change-notification links for participating engines. It does not submit ordinary pages to Google or guarantee ranking. Once the technical route is correct, spend effort on useful page information rather than repeatedly notifying engines about unchanged pages.
References and further reading
Continue with a practical task
Browse all guides or choose a free tool. All examples are illustrative; replace assumptions with your own verified details.