inemaSEO 1 — Foundation: the X-ray and the groundwork of your site|INEMA.CLUB-PRO

Lesson 8 · 18 min

Notify the search engines and check indexing

With the foundation ready, every publication closes with two steps: notify the search engines that the URL exists and, a few days later, check whether it made it into the index. Notifying a broken URL burns trust; not checking leaves an important page forgotten. At the end, you build the dated plan for the whole course.

Start the lesson
A mail carrier delivers envelopes to a mailbox and checks the clipboard.

In this lesson you will

  1. 1Publish the IndexNow key
  2. 2Notify only with URLs that return 200
  3. 3Read the URL Inspection statuses
  4. 4Build the dated foundation plan

Goal: notify IndexNow and Bing only with URLs that return 200, and check indexing in URL Inspection.

01From commit to indexed page

Tap each block.

Click each block in the diagram to see what it does.

Notifying is cheap; notifying wrongly is expensive. That's why the 200 check comes first.

02Notify and check without stumbling

Tap each step.

1. The key

Create a key of 32 or more hexadecimal characters (numbers and letters from a to f) and publish it at https://seusite.com/[sua-chave].txt, with only the key inside.

It isn't a secret: it's public by design, and it proves the site is yours.

At INEMA (10/02/2026)The news site's first submission came back 403 SiteVerificationNotCompleted: the key had just been published. Resubmitting after about 4 minutes fixed it.

03The files and the commands

Replace what's between < > with your own. The Bing key is optional.

urls.txt (one per line)
https://www.seusite.com/
https://www.seusite.com/pagina-nova/
https://www.seusite.com/pagina-mudada/
Terminal · notify (IndexNow, and Bing if you have a key)
INDEXNOW_KEY=<sua-chave> bash tools/avisar_buscadores.sh urls.txt

# optional, with the Bing Webmaster API key:
INDEXNOW_KEY=<sua-chave> BING_API_KEY=<chave-bing> BING_SITE=https://www.seusite.com/ bash tools/avisar_buscadores.sh urls.txt
Terminal · batch inspection (template; needs a Google credential)
# requires authenticated gcloud and GSC_QUOTA_PROJ set
python3 tools/gsc_inspecionar.py sc-domain:seusite.com https://www.seusite.com/pagina/
Check log (template)
| URL | notified on | inspected on | status | Google canonical | next step |
|---|---|---|---|---|---|
| </pagina-nova/> | <dd/mm> | <dd/mm> | <Submitted and indexed> | <same> | <none> |
Simulation: illustrative example
IndexNow: HTTP 202

If a URL doesn't respond with 200, the script stops before sending:

NÃO 200 (404): https://www.seusite.com/pagina-errada/
corrija as URLs acima antes de avisar

04Practice: your first notification and your first check

E2 asks for a few days between notifying and inspecting.

E1 · Key and first notification

30 min

Publish your IndexNow key on your site, build the urls.txt file with 3 to 5 URLs, and run avisar_buscadores.sh.

Done when: the script responded IndexNow: HTTP 200 or 202 and no URL was rejected for not responding with 200.

E2 · Five URLs inspected

25 min

A week later, inspect your 5 most important URLs in Search Console and fill in the log.

Done when: the log has 5 rows with status, crawl date, and Google's canonical; the ones that aren't indexed have a next step.

05Test what you learned

The explanation appears after you answer.

Question 1 of 4

Why does the script check for a 200 before notifying?skill

06The foundation map

Four steps and the exercises for each one. Click an exercise to see its "done when".

Week 1Look

read-only X-ray

2 exercises

raio-x.txt and a list of findings.

View the lesson
Week 1Dashboards

Search Console and Bing

2 exercises

Site verified and sitemap submitted in both.

View the lesson
Weeks 2 and 3Foundation

canonical, sitemap, robots, thin page (lessons 4 to 7)

2 exercises

One address, a true sitemap, bots decided, thin pages out of the index.

View the lesson
Week 4Notify

IndexNow, Bing, and inspection

2 exercises

First notice sent and 5 key URLs checked.

View the lesson
By the end of the courseYour site, read the way a search engine reads it, verified in both dashboards, with a technical foundation and a routine for notifying and checking.
16 exercises
Click an exercise to see what to do and the "done when".
  1. 1/5

    Look

    Before you touch anything, take the picture. The list of findings becomes your plan for the following weeks.

  2. 2/5

    Dashboards

    Requires the X-ray. Check your DNS before creating an account; the reports start to fill up in a few days.

  3. 3/5

    Foundation

    Requires the dashboards. These are lessons 4 to 7; the map shows the exercises from lesson 6, and the plan below lists them all.

  4. 4/5

    Notify

    Requires the foundation: sending notices before fixing the canonical is inviting the search engine to see the mess.

  5. 5/5

    The whole foundation

    Look, verify, fix the foundation, and notify. Only move up a step when the "done when" of the previous one is true.

After the foundation comes course 2: the pages only you can write.

07Generate your plan with dates

Pick a start date and how much time you have each week. The plan respects the exercise that asks for a week of waiting.

08Takeaways

200 firstOnly notify a URL that returns 200.
Two pathsIndexNow and Bing for Bing and partners; sitemap and inspection for Google.
2026 yardstickBing matters for Copilot and, per a Seer study, for ChatGPT. A notice is not a guarantee of citation.

Going further

IndexNow: documentation (English)avisar_buscadores.sh on GitHubinemaSEO Area in EventosNext: inemaSEO 2 · Content
Previous lessonBack to the start of the course