Pievienot vietni Search Console

Kad izmantot

The company's site is live (or about to be) and nobody has a verified Search Console property for it yet. Not for getting the site indexed better over time — that is growth.seo-monthly, which uses this property as its input. Not for a domain the company does not yet hold — register it first with tech.register-domain.

Pirms sāc

• The site answers on its final domain over HTTPS (a staging URL is the wrong property).
• You know which Google account is the company's — not a founder's personal one.
• You can edit DNS records in the zone (bc dns), and you know whether the whole domain or only one subdomain is in scope.

Ko izpilde pieprasa1

Ceļš7 soļi

1. S1

   Check prerequisitesaģents

   Confirm the domain resolves, HTTPS works, and the zone is served by Brain Club nameservers. Note who the site is for.

   Izdarīts, kad the site opens over HTTPS and the zone location is known.

2. S2

   Choose the property typeaģents

   Prefer a Domain property (covers all subdomains and both protocols, verified by DNS). Use URL-prefix only when the site lives on a subdirectory of a domain the company does not control. Record the choice and the reason.

   Izdarīts, kad the property type and its reason are written down.

3. S3

   Create and verify the propertyaģentsvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S3 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   In the company's Google account, create the property, choose DNS verification, and copy the TXT token. Publish the TXT record in the zone (bc dns — host @ or the named host, value = the token Google gives, TTL default). Trigger verification in Search Console.

   Izdarīts, kad Search Console shows the property as Verified.

   ⛔ The token is a live record, not a comment — deleting it later un-verifies the property. Never paste it with quotes or line breaks added by the editor. ⚠ jāpārbauda current verification methods and record format in Search Console Help (support.google.com/webmasters) — Google changes this UI.

4. S4

   Submit the sitemapaģents

   Find the sitemap (usually /sitemap.xml); if the site has none, note it as a gap for growth.seo-monthly instead of inventing one. Submit the URL in Search Console.

   Izdarīts, kad the sitemap URL returns HTTP 200 and appears in the Sitemaps list with a status.

5. S5

   Check the site is indexableaģents

   Fetch https://<domain>/robots.txt — it must not disallow the sitemap or /. Check the homepage has no noindex left from staging. Request indexing for the homepage once.

   Izdarīts, kad robots.txt allows crawling and the homepage has no noindex.

6. S6

   Grant accessaģents

   Add the owner as Owner (or Delegate, per the account's structure) and any named staff as Full or Restricted, per the access list from Before you start.

   Izdarīts, kad the property's settings list every named person with the agreed role, and no personal accounts beyond the company account.

7. S7

   Record and hand backaģents

   Link the property to the goal/task it serves (bc tasks add or bc goals add — name, domain, property type, who has access). Add the property to the growth.seo-monthly routine. Send the owner a three-line summary: property, verification method, what is now tracked.

   Izdarīts, kad the property is linked to its goal/task, added to the growth.seo-monthly routine, and the owner has the three-line summary.

Pārbaudes — kā zinām, ka izdevās

• Search Console shows Verified (read it back from the UI, not from the verification attempt log).
• The TXT record is still present in the zone and its value matches the token character for character.
• The sitemap status in Search Console is not "Couldn't fetch".
• robots.txt fetched from the live domain allows the sitemap and the homepage.
• The owner's access is at owner/delegate level, shown in the property's users list.

Ja noiet greizi

Ko atstāj katrs solis

1. S1the site opens over HTTPS and the zone location is known.
2. S2the property type and its reason are written down.
3. S3Search Console shows the property as Verified.
4. S4the sitemap URL returns HTTP 200 and appears in the Sitemaps list with a status.
5. S5robots.txt allows crawling and the homepage has no noindex.
6. S6the property's settings list every named person with the agreed role, and no personal accounts beyond the company account.
7. S7the property is linked to its goal/task, added to the growth.seo-monthly routine, and the owner has the three-line summary.

Ko saglabāt

Property type and URL · the TXT record value and zone it sits in · verification date and the Google account used · sitemap URL and its status · the access list from S6 · the owner's approval in S3 (who, when).

Kā šī procedūra uzlabojas

After every 10 runs ask: how long from ask to verified, and did verification ever need a second attempt — and why? Did any property lose verification because its TXT record was cleaned up? Was URL-prefix ever chosen where a domain property was possible? A new version changes the step behind the wait or the loss, and says so in its change note.