LessonsHow to help Google find your website

Mini lesson 22 of 30 · Reach people and offer services

Separate visibility from ranking

Who is this for?

People who cannot find their website in Google and want a practical diagnosis. A coding assistant can make the supplied page-file changes; you focus on access, ownership and observed search status.

A missing name-search result does not tell you whether Google indexed the page.

Purpose of this lesson

  • Check whether the intended public page is accessible and eligible.
  • Verify the correct Search Console property and page.
  • Separate requested indexing, observed indexing and ranking.
Explanation, worked example and practice

Before you start

Your own Google account and a public HTTPS practice page you control. The workshop supplies before/after files; publishing and ownership verification require your own real account/site. You may report a precisely blocked stage.

Check your starting skills

These are useful skills, not locked course requirements. If you can already do them, start this lesson; otherwise open the linked preparation. The supplied starter files mean you do not need an existing personal website.

  1. How to publish your website from GitHub

    Connect a practice repository to hosting.

Estimated time: 26–44 min

Estimates for the supplied starter files with prerequisite accounts and tools ready. Setup, deployment queues and delivery/DNS waits take additional time. Planning estimates with an editable public site ready. DNS propagation, crawling and indexing waits are additional; Google may take days or weeks and does not guarantee inclusion.

Understand the idea

Open your intended public page and note the exact final address. Choose a small search-readiness question: can a signed-out visitor reach it, and what does Google report about that URL?

A live page and a first-page search result are different observations. Do not diagnose “not indexed” from ranking alone.

A concrete example

You can open a page signed out and still fail to find it in a name search. The first observation proves public access; indexing and ranking need their own checks.

Use the supplied search-readiness files and my owned public practice page. First inspect access and accidental indexing blocks. Explain proposed changes before editing; do not make private pages public. Help publish the intended fix, verify my Search Console property with its actual issued method and inspect the exact URL. Record eligibility, indexing request and observed indexing separately; do not promise first-place ranking.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

Your homepage opens in a private window but is absent from a name search. What do you know, and what remains to be checked?

Show a worked solution

The homepage is publicly reachable in that test. I do not yet know whether Google indexed it or where it ranks. I would inspect its exact URL in my Search Console property before diagnosing an indexing problem.

What a sound answer includes

  • Distinguishes public access from indexing and ranking.
  • Chooses URL Inspection as the next indexing check instead of assuming a cause.
How it works (optional)

Make the page accessible before chasing a ranking

We can control our site and submit evidence. We cannot promise that Google will index a page or put it first.

A public page can be available on the web without appearing in Google’s index. An indexed page can also appear too low for a particular query. Those are different situations and need different investigations.

This lesson finishes when you have checked a public page, investigated blockers, verified ownership, submitted a correct sitemap and recorded the inspection result. “Requested” or “waiting” is a valid recorded status; it is not the same as “indexed”.

On emrevarol.com, a concern about search visibility led us to inspect site verification and discovery. The workshop below uses a fictional portfolio so you can examine every file without guessing what changed on a real site.

Worked example: the browser works, the search result does not

Alex can open a portfolio URL directly, but searching a name produces no obvious result. The page might be unindexed, indexed under another canonical URL, or simply not prominent for that query.

Check the URL and available inspection evidence before rewriting the entire site.

Google: get your website on Search

Extra implementation exercise

A portfolio opens at its public URL but does not appear in the first page of results for the owner’s name. Does this prove that Google has not indexed it?

Show a worked solution

No. A page can be indexed without appearing prominently for that query. Use Search Console’s URL Inspection for the page you control and record what it actually reports.

A site: search can offer a clue, but it does not necessarily list every indexed URL.

  • Distinguishes absence from the first results page from proof of non-indexing.
  • Uses URL Inspection or other appropriate evidence before choosing an indexing or ranking diagnosis.

Step 1 · How to help Google find your website

Check signed-out access first

Google needs a route that does not depend on your owner session.

Explanation, worked example and practice

Understand the idea

Open the page in a private window and try its main content. If you see a login or password screen, ask the assistant to inspect whether this page is intentionally private.

Do not remove protection from genuinely private content. An inaccessible intended-public page needs an access repair before title or sitemap polishing.

A concrete example

If the private window shows the site owner’s login screen, Google does not have the same access as the signed-in owner. If that page is intentionally private, it should stay private.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

What did the signed-out visit actually return?

Show a worked solution

Illustrative blocked result: the private window shows a password screen instead of the homepage. This is intended to be a public practice homepage, so access is the first issue to fix. If it were a private review draft, I would leave the protection in place and choose a different public page.

What a sound answer includes

  • Describes the signed-out response, including any login barrier.
  • Distinguishes an accidental barrier on a public page from intentional private access.
How it works (optional)

Check the exact public URL

Use the URL a visitor should reach, including HTTPS, hostname and path.

Open the public URL in a private browser window. Check whether the page loads without your owner account, whether its main content is visible and whether the final address is the one you intend to publish.

Inspect the network response or use your browser’s developer tools. A redirect may be intentional; follow it and inspect the final page. A 404 page styled to look attractive is still a failed destination.

An access check is only the first boundary. A successful response does not prove indexing eligibility, indexing, or ranking.

Worked example: a preview URL is not your final site

A private preview may deliberately require login or contain noindex. That is appropriate for a draft. Use the intended public production page for this exercise.

The mini-lesson preview you are reading is deliberately not published for indexing. Do not remove its protections as part of the assignment.

Google: get your website on Search

Extra implementation exercise

Your homepage works while logged in to the host, but a private window opens a password screen. Which result should you record before investigating titles or sitemaps?

Show a worked solution

Record that the expected public page is not accessible to a visitor without credentials. Check the production URL and intentional access settings first.

Do not make a private site public merely to complete the lesson. Use a separate practice site when access restrictions are intentional.

  • Records that the intended public page is not yet accessible without credentials.
  • Checks the intended public URL and access configuration rather than claiming that metadata alone will solve it.

Step 2 · How to help Google find your website

Remove only accidental search blocks

Have the assistant inspect the supplied before/after example.

Explanation, worked example and practice

Understand the idea

Ask the assistant to open the supplied before/index.html and before/robots.txt. The page asks search engines not to index it, while robots.txt blocks crawling. Compare them with the after files and have the assistant explain the two different restrictions.

For your intended public page only, approve the corresponding repair and publish it. Recheck the files actually served at the public address; changing a local copy does not update what Google can fetch.

A concrete example

The supplied before page contains noindex, and before/robots.txt contains Disallow: /. Removing only the vague “Home” title leaves both restrictions unchanged. A robots.txt block can also prevent a crawler from seeing the page’s noindex instruction.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

Which accidental block, if any, did you find and verify after publication?

Show a worked solution

In the supplied before example, I found noindex in the page and Disallow: / in robots.txt. For this intended public site, the assistant should remove the accidental indexing restriction and allow the intended crawl path. I would then inspect the published HTML and robots.txt; private drafts keep their protection.

What a sound answer includes

  • Identifies the page’s noindex instruction and the separate crawling block.
  • Checks the published public response after the intended repair.
How it works (optional)

Find the blockers in the example files

A page can ask search engines not to index it, prevent crawling, or nominate a different canonical URL.

A noindex directive tells supporting search engines not to index a page. It can appear in the page’s robots meta tag or an X-Robots-Tag response header. Inspect the final response as well as the HTML.

A robots.txt crawling rule is different from noindex. Blocking a crawl can prevent Google from seeing the current page’s indexing instructions. Do not use crawling rules as a substitute for keeping private information behind authentication.

A canonical link suggests the preferred URL for duplicate or closely related content. A link left pointing at an old site is evidence to investigate; it does not by itself guarantee which URL Google will choose.

Check both the rendered page's raw HTML robots metadata and the site's robots.txt at the exact intended public origin. A robots.txt block controls crawling; it does not reliably remove an already known URL from search. A blocked crawler also cannot read a new noindex tag. Decide whether this page should be public before changing either control.

Worked example: deliberate faults in the starter

Open before/index.html and before/robots.txt. This fictional portfolio has a noindex tag, an unrelated canonical URL, and a crawling rule that blocks every path.

The short title is vague, but changing it alone does not address these blockers.

<title>Home</title>
<meta name="robots" content="noindex">
<link rel="canonical" href="https://old-portfolio.example/">

Google: noindex directives · Google: robots.txt basics · Google: canonical URLs

Extra implementation exercise

The page is meant to be public, but its HTML has noindex and its robots.txt contains Disallow: /. Why is changing only the title insufficient?

Show a worked solution

The title does not remove either the noindex directive or the crawling block. Investigate both settings and correct the accidental ones for this public page.

Make sure Google can fetch the intended page and see the corrected indexing instructions.

  • Identifies the noindex instruction and the crawling block as separate issues.
  • Checks both accidental blockers on the intended public site; does not remove deliberate privacy protections.

Step 3 · How to help Google find your website

Use your real canonical address

Example placeholders must not survive into the public page.

Explanation, worked example and practice

Understand the idea

Tell the assistant your real public HTTPS address. The after template still uses https://YOUR-REAL-SITE.example/; it must replace that reserved placeholder consistently in the page’s preferred-address setting, robots.txt sitemap reference and sitemap entries.

The preferred address, also called the canonical URL, identifies which version of a page you want search engines to treat as the main one. Ask the assistant to show the configured value on the published page, then open that exact address.

A concrete example

The supplied before page points its canonical URL to https://old-portfolio.example/. Even if its visible name is correct, that setting describes the wrong site.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

The supplied template still identifies https://YOUR-REAL-SITE.example/ as its main address. What needs changing before you submit your own site?

Show a worked solution

The reserved .example address is not my public site. I would give the assistant my actual HTTPS homepage URL and ask it to replace the template origin in the page, robots.txt sitemap line and sitemap entries. I would open those published addresses before submitting anything to Google.

What a sound answer includes

  • Recognizes the .example address as an unconfigured placeholder.
  • Keeps the page’s preferred address and sitemap references consistent with the real HTTPS site.
How it works (optional)

Publish a clear page at the intended address

Use the reference files as a template, replacing the example addresses with your real site.

Open after/index.html. It has a descriptive title and description, and no accidental noindex tag. The canonical URL still contains a visible placeholder because the lesson does not know your domain.

Replace every https://YOUR-REAL-SITE.example/ value with the real public URL you intend to use. Then publish through your normal review process and inspect the delivered page again. Do not submit the reserved example address to Google.

Keep the page’s useful content visible and navigable. Metadata describes the page; it does not replace having relevant work, readable text and working links.

Worked example: a page-specific title

“Alex Morgan · Accessible websites for small businesses” tells a visitor more than “Home”. The description briefly explains the actual work shown by the page.

The title and description are inputs Google may use, not a promise that a search result will reproduce them exactly.

<title>Alex Morgan · Accessible websites for small businesses</title>
<meta name="description"
      content="Alex Morgan builds accessible websites for small businesses. Explore recent projects and get in touch.">
<link rel="canonical" href="https://YOUR-REAL-SITE.example/">

Google: title links

Extra implementation exercise

A learner copies the reference file and leaves its canonical URL as https://YOUR-REAL-SITE.example/. What must they replace and verify before using this template on a real site?

Show a worked solution

Replace the placeholder with the actual preferred public URL. Publish the change, inspect the delivered head, and open the canonical destination.

A file edited on your computer is not proof of what the host currently serves.

  • Replaces the placeholder with the intended real public canonical URL.
  • Checks the delivered HTML and the destination URL after publishing.

Step 4 · How to help Google find your website

Verify the right Search Console property

Use the method issued to your own account/property.

Explanation, worked example and practice

Understand the idea

Create or select a URL-prefix Search Console property for the public HTTPS site you control. Use one verification method actually offered to that property. If you choose an HTML tag, the assistant can place Google’s exact issued tag in the real homepage and publish it before you select Verify.

If verification fails, compare the chosen property with the public address and inspect whether the issued tag or file is visible there. Keep a successful verification method in place; you do not need to give the assistant your Google password.

A concrete example

A correct verification tag saved only on your laptop is invisible to Google’s remote check. The next action is to publish and inspect it, not to invent a new token.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

Google says it cannot find your verification tag, which you saved locally. What should you check before retrying?

Show a worked solution

I would open the property’s public homepage signed out and ask the assistant to inspect its delivered source for the exact tag Google issued. If the tag is only local, I must publish it first. A successful ownership check would establish access to the property, not that the page has been indexed.

What a sound answer includes

  • Checks that the exact issued value is published on the correct property’s public homepage.
  • Keeps verification separate from indexing success.
How it works (optional)

Verify ownership in Search Console

Ownership verification gives you access to diagnostics for the site you control.

Open Search Console in your own Google account and add the exact site as a URL-prefix property. This route is specific to a protocol and hostname; a Domain property covers a different scope and normally requires DNS verification.

Choose an available verification method. If using the HTML-tag method, copy the exact tag Google supplies into the real homepage’s head, publish the page, then return to verify. Use an alternative method offered for your site if the tag method is unavailable.

Keep the verification method in place after success. The value in an HTML verification tag is meant to be public; it is not an email-service or AI API key. Never paste an unrelated secret into it.

Worked example: exact values matter

For the HTML-tag method, the name is google-site-verification. The content value must come from your own verification flow; a made-up example value cannot verify ownership.

<!-- Copy the ACTUAL tag Google gives you into the homepage head. -->
<meta name="google-site-verification" content="YOUR_ACTUAL_GOOGLE_VALUE">

Google: verify site ownership · Google: property types

Extra implementation exercise

You edited the tag locally, clicked Verify, and Google says it cannot find the tag. What two checks come before generating a different value?

Show a worked solution

Check that the edited page was published and that the exact tag appears in the public homepage’s head. Then check that the property and final URL match the site you edited.

Do not replace the token with a guess. A redirect to a different homepage can also explain why you are inspecting the wrong delivered page.

  • Publishes the edit and checks the publicly delivered homepage head.
  • Confirms the exact URL-prefix property, final homepage URL and original Google-supplied value.

Step 5 · How to help Google find your website

Check the sitemap’s destinations

Include only public pages that really belong there.

Explanation, worked example and practice

Understand the idea

Ask your assistant to prepare or inspect the supplied sitemap using real canonical public URLs. Open the listed destinations and submit it through the intended property when appropriate.

Remove accidental private preview and missing-page entries from a public sitemap. Do not publish sensitive URLs merely to fill a list.

A concrete example

The supplied sitemap lists one homepage. After replacing its placeholder origin, opening that entry should reach the intended public homepage. A password-protected review draft and a deleted 404 page stay out.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

Your proposed sitemap contains the public homepage, a password-protected draft and a deleted page. Which entries belong, and what should you verify?

Show a worked solution

I would keep the intended public homepage after opening its exact preferred URL. I would remove the private draft and deleted page. After publishing the sitemap, I would record whether the correct Search Console property received it; receipt alone does not mean its pages were indexed.

What a sound answer includes

  • Keeps accessible canonical public pages and excludes private or missing pages.
  • Separates checking destinations from Search Console’s sitemap-submission status.
How it works (optional)

Submit a small, accurate sitemap

A sitemap helps describe URLs you want discovered. It is not an instruction that forces indexing.

Open after/sitemap.xml and after/robots.txt. Replace the placeholder base address with your real HTTPS site. List the public canonical pages you intend people to find, not private previews or error pages.

On the one-page practice site, publish the supplied files at the root after replacing the address. On an existing site, keep its intentional crawling rules and public URL entries; merge your correction instead of overwriting the whole robots.txt or sitemap. Open the published sitemap, check the expected XML, then submit it in the verified property.

For a small practice site, one real homepage URL is enough to understand the flow. A sitemap is not required for every page to be found, and successful submission does not guarantee that every listed page will be indexed.

Worked example: one intended page

The location inside this XML must be your actual public page. The same base address should be used consistently in the canonical link and the sitemap.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url><loc>https://YOUR-REAL-SITE.example/</loc></url>
</urlset>

Google: build and submit a sitemap

Extra implementation exercise

Your sitemap contains a private preview URL that requires login and an old page that returns 404. Should these remain in this public sitemap?

Show a worked solution

No. Remove those entries from this public sitemap and check the actual pages you intend to make discoverable.

A syntactically valid XML file can still list the wrong destinations.

  • Removes the private preview and missing page from the intended public URL list.
  • Checks each remaining public canonical URL instead of equating a parseable sitemap with a correct sitemap.

Step 6 · How to help Google find your website

Inspect the page’s reported status

A request accepted is not the same as indexing complete.

Explanation, worked example and practice

Understand the idea

Use URL Inspection for the exact page and read its reported state. Run the available live check and request indexing when appropriate for the intended public page.

Record eligibility, request receipt and indexed status as different facts. Neither a verified property nor an accepted request promises a ranking.

A concrete example

An illustrative status can be: the live check says the page is available to Google; the indexing request was accepted; the indexed result still says the URL is not on Google. That is a pending result, not a contradiction to hide.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

What did Google actually report for eligibility, request and indexing?

Show a worked solution

Illustrative record: live eligibility passed; the indexing request was accepted; the reported indexed status is still “URL is not on Google”. I would leave indexing pending and check the reported state later. Neither the request nor property verification establishes a first-page ranking.

What a sound answer includes

  • Reports live eligibility, indexing-request status and indexed status separately.
  • Does not infer a ranking or completed index from an accepted request.
How it works (optional)

Inspect the URL and record the actual status

Read the result before deciding what to fix or whether to wait.

Use URL Inspection for the exact public page. Distinguish information about Google’s known indexed version from a live test of the page currently served. The two may reflect different moments.

If the live test reports an issue, investigate that issue first. If appropriate and available for your page, request indexing after correcting it. Record the result and time instead of repeatedly clicking the request button.

An eligible live page or an accepted request does not guarantee inclusion or ranking. Revisit the report later; if it remains unindexed, use the reported reason and the quality of the actual page to guide the next step.

Worked example: an honest status note

A note such as “Public page loads; ownership verified; sitemap submitted; live test passed; indexing request recorded; not yet indexed” tells the truth and gives you a next observation to make.

Do not replace that note with “SEO complete” or promise a first-page result.

Google: URL Inspection · Google: get your website on Search

Extra implementation exercise

The live test says the page can be indexed and your indexing request is accepted. Can you report that the page is already indexed and will rank first?

Show a worked solution

No. Record eligibility and request acceptance as those specific observations. The indexed status and ranking remain separate outcomes.

Save the inspection result and check again later rather than claiming a result the report does not show.

  • Separates live eligibility and request acceptance from actual indexing.
  • Does not promise a ranking; records the current status and a later follow-up.

Step 7 · How to help Google find your website

Finish a useful readiness record

Connect observations to a change and next action.

Explanation, worked example and practice

Understand the idea

Complete the worksheet for one owned public page. Include a before/after observation or the precise reason a controllable step remains blocked.

Explain the last verified stage and the next check. Remaining Google crawl/index timing is not a reason to claim an unseen result.

A concrete example

A useful next action follows the last result: if ownership fails, repair verification; if ownership and live eligibility pass but indexing remains pending, retain the exact URL and revisit its reported status.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

Try it yourself

Provide your URL, real diagnostic record and one next action.

What to produce: A redacted search-readiness record with the actual URL, checks, changes and remaining status.

Show a worked solution

Illustrative diagnosis: the intended public homepage was reachable; the assistant removed the supplied accidental noindex/crawl block and replaced the wrong canonical origin; published files were rechecked. Ownership and sitemap receipt passed, but indexing remains pending. My next action is to inspect that same URL’s reported status again, rather than change the page title repeatedly.

What a sound answer includes

  • Connects the exact public URL, completed diagnosis and any published correction.
  • Names one next action that follows the remaining blocker or reported Google status.
How it works (optional)

Your assignment: produce a search-readiness record

Complete the checks for one site you own and explain any unresolved boundary.

Choose one public page you control. Record its final URL and access result, indexing directives, canonical address, ownership status, sitemap result and URL Inspection status.

Use the worksheet to separate what you changed from what you observed. If you cannot complete ownership verification or the page remains unindexed, report that honestly and explain the next action.

The assignment is complete when the controllable steps are demonstrated and the remaining status is accurately documented. An indexed result is useful additional evidence, not a promise this lesson can make.

Worked example: explain one diagnosis

“The public homepage contained noindex. I removed the accidental directive from production, verified the delivered response, and ran a live inspection. The request is recorded; indexing is still pending.”

That explanation connects an observation, a change and a new check. It is more useful than listing tools you opened.

The complete reference walkthrough is available in reference/assignment-walkthrough.txt. Compare its steps with your own result; fill the test record from observations in your own project.

Extra implementation exercise

Create the search-readiness record for one public page you own. Include one before/after observation or a precise explanation of why a step is still blocked.

  1. Check the final public response, robots instructions and canonical URL.
  2. Verify the correct property and submit a real sitemap if appropriate.
  3. Inspect the page and record eligibility, request and indexing as distinct observations.
Show a worked solution

Use the exact public canonical URL you want people to find. Fetch it signed out and verify a successful HTML response with substantive content. For this intended public page, inspect and resolve both an accidental noindex and a whole-site crawling block; do not apply those changes to private review pages.

Add the exact verification tag issued to your own property to its public head, publish it and inspect raw public source before clicking Verify. Keep that verification method in place after success. The tag is not your account password.

Include only accessible canonical pages in the public sitemap, submit it through the intended Search Console property and inspect the URL's reported status. A received sitemap or verified property does not guarantee indexing/ranking; report Google's observed state and any pending crawl.

  • Uses the intended real public URL and demonstrates the relevant delivered settings.
  • Records ownership and sitemap/inspection results without invented success.
  • Separates site-controlled work from Google’s indexing and ranking decisions.

Was this lesson useful?

Leave a like, or share it with someone who could use it.