You search for your company or a service you offer, but your website does not appear. That does not necessarily mean Google has no record of the page. It could be indexed but rank poorly, or appear for different searches from the one you tried.
Start with one important URL, such as the homepage or a service page. This guide helps you choose the next action from evidence rather than changing every SEO setting. Record the URL, Search Console's finding and the date of each change so you can follow the investigation.
Step 1: Identify the exact missing URL
Open the page in a private browser window while signed out. Does the expected content appear? If it redirects, note the final address. HTTP versus HTTPS, www versus non-www, and old versus new paths can mean you are checking the wrong version.
A site:your-domain.se search can offer a quick clue, but it is not a complete inventory of Google's index. Use Search Console to investigate the specific page.
Step 2: Inspect the URL in Google Search Console
Open Google Search Console, choose the correct verified property and paste the complete URL into URL Inspection. The property owner or administrator may need to grant you access.
Google's URL Inspection guidance distinguishes information about the indexed version from the live test of the current page. These can differ after an update.
Choose the relevant path:
- URL is on Google: continue to step 7. You may have a visibility problem for a particular query.
- URL is not on Google: expand the page-indexing reason and follow the corresponding check below.
- The page redirects, or Google selected another canonical: start at step 5 and identify which URL is treated as the main version.
Passing the live test does not guarantee indexing.
Step 3: Resolve access and crawling problems
If robots.txt blocks the page
Ask your developer to check the rules affecting this URL and Googlebot. A rule left over from a staging site can prevent important content from being fetched. Remove accidental restrictions only; do not expose private areas to solve an SEO issue.
Google distinguishes robots.txt from indexing controls. Robots.txt manages crawling and is not a reliable way to keep a URL out of search results.
If the server or access controls prevent fetching
Check HTTP status, outages, login requirements and whether a firewall presents a challenge page to Googlebot. One possible fault is a page that works for a signed-in administrator but returns an error to everyone else.
Ask the developer to fix the cause and retest. A normal public content page should generally return 200. A page that looks correct in your browser may still return 404 or 500. Do not turn genuinely missing pages into 200 responses simply to hide a report error.
Step 4: Check for noindex in the page and response
An “Excluded by noindex” finding means Google encountered an instruction not to index the page. That instruction can be in a robots meta tag or the X-Robots-Tag HTTP header. A CMS visibility setting may add it.
For a page intended to be public, ask the developer to remove accidental noindex instructions, clear relevant caches and inspect the response again. Google needs to crawl a page to read its indexing instruction. Blocking it in robots.txt at the same time can interfere with processing the update.
Keep intentional noindex for content that should not appear in search. It does not replace authentication for private information.
Step 5: Check whether Google chose a different URL
Compare the user-declared canonical with Google's selected canonical in URL Inspection. An old domain, wrong language version or homepage used as a general canonical can point to the cause.
If the page intentionally duplicates another, exclusion from separate indexing may be correct. If it serves a distinct purpose, ask the developer to review canonicals, redirects and internal links together. They should consistently identify the intended URL. Canonicals are signals, not guarantees of Google's selection.
Avoid changing an established address just to try a new keyword. Unnecessary moves add more variables to the investigation.
Step 6: Help Google discover the intended page
Confirm that a relevant public page links to it with a normal crawlable link. A published page reachable only by typing its address can be difficult to discover.
Open the XML sitemap and check that it includes the correct public URL rather than redirects or staging addresses. Search Console's sitemap report shows whether Google could read the file. A sitemap helps discovery but does not guarantee indexing.
For “Discovered – currently not indexed”, check discovery and access first. For “Crawled – currently not indexed”, also examine duplication and whether the page offers a distinct useful answer. Creating several near-identical pages for the same service is not a useful remedy.
For a JavaScript-based site, ask the developer to check the content available to Google after rendering. A visible page header is not enough if the actual service description is missing.
Step 7: If the page is indexed, investigate the search query
Filter Search Console's Performance report to the page and examine queries and impressions. A single search from your own device is affected by factors such as location and context and cannot give the full picture.
Does the page answer the prospective customer's particular question? A homepage might explain the company without addressing a detailed service query. Improve relevant content and clarity before adding more pages covering the same ground. Indexing and strong rankings are different outcomes; a new page has no guaranteed position or fixed time to results.
If the entire site disappears suddenly, also check Search Console's security-issues and manual-actions reports. Do not assume a penalty without supporting evidence.
Step 8: Retest the change and follow up
Run another live test after fixing the fault. Request indexing once for an important updated page and submit an updated sitemap when appropriate. Google says recrawling can take days to weeks, without guaranteeing indexing. Repeated requests do not speed up crawling.
Follow up to see whether the reported reason changes and impressions begin to appear. Keep the change log so you can distinguish older report information from the current page.
For preventive maintenance, use our existing technical SEO checklist. If you need help fixing an identified issue, explore our web development services. If the problem is part of a website project, describe the situation in Irozon's website planner. Include the affected URL and error message, but never share login credentials.