Mida su töötaja teab enne, kui ta midagi ehitab.
Igaüks võib näidata mudeli veebilehel. Need on reeglid, mida kohaldatakse iga lehe, miks iga üks olemas, ja kes neist peatada avaldamist, mitte hoiatada.
Iga reegel allpool oli makstud intsident saidil me jookseme ~ pingerea kalju, katkine tõlge, leht, mis muutis oma lähtekoodi. Me ei ole arvamine parima tava; me kirjutame üles, mis juba läks valesti, nii et see ei lähe valesti saidil liiga.
Reeglid, mis blokeerivad avaldamise otse: 8 of 12. Blokeeritud leht antakse töötajale tagasi põhjusega, ja see üritab uuesti. See ei avalda ja hoiatada teid pärast.
1. One page, one subject
plokid avaldatakse
Exactly one <h1>. A descriptive <title> of 15-60 characters.
Miks?: Title is the strongest per-page signal Google has. Google rewrites titles for the SERP most of the time, but the signal it forms from yours still affects ranking, and a generic or duplicated title reads as a quality problem.
2. A description written for a human
hoiatus
A meta description of 140-158 characters, unique to the page.
Miks?: Description does not rank the page, it decides whether anyone clicks it. Too short wastes the snippet; too long truncates mid-sentence.
3. No shared body text, ever
plokid avaldatakse
Every page gets body copy and FAQ answers written for that page. Never a shared template with a noun swapped in.
Miks?: This is the one that costs months. A site we run shipped ~1700 pages on one generic FAQ body and a site-level quality classifier suppressed the whole domain — pages still indexed, ranking gone, no manual action to appeal. Recovery ran on core-update timescale.
4. Absolute canonical, paired with hreflang
plokid avaldatakse
Every page self-canonicalises with an absolute URL. Any hreflang cluster ships alongside that canonical, also absolute.
Miks?: Relative hrefs are silently dropped. hreflang without a self-canonical fills the index report with "Duplicate without user-selected canonical" — 56,801 pages on one site we run.
5. Markup may only claim what the page shows
plokid avaldatakse
Structured data mirrors the visible text exactly. Schema goes on the page types that earn a rich result, not on everything.
Miks?: Schema is not a general ranking input and not required for AI search -- Google says so directly. Markup that claims a price or a question the page never shows is a violation that can earn a manual action.
7. Positional {0} slots in translatable strings
plokid avaldatakse
Any string that will be machine-translated uses {0}, {1} — never {name}.
Miks?: MT engines translate or transliterate the word inside the braces, or drop a brace entirely. A numeric slot has no word to translate and survives intact. This silently broke about 10% of non-English rows on one site before anyone noticed.
8. Nothing is indexable until it is finished
plokid avaldatakse
Pages ship noindex. Indexing is a deliberate opt-in by the owner, per site.
Miks?: These sites share a wildcard domain. One spam tenant indexed on that wildcard damages every other tenant on it, and a half-finished page indexed on day one takes months to undo.
9. Build the thing, do not describe the thing
hoiatus
A page either does something useful or says something specific. A page that only describes a tool is not a page.
Miks?: Thin wrappers around someone else's API are the clearest signal a quality classifier has. Real utility is what survives a core update.
10. No orphans
hoiatus
Every indexable page has at least one inbound internal link.
Miks?: Internal links pass ranking signal and drive crawl. A page reachable only from the sitemap gets crawled a few times and then largely forgotten.
11. Alt text and intrinsic dimensions on every image
hoiatus
Every <img> has alt text and explicit width/height.
Miks?: Alt text is an accessibility requirement first and an indexing signal second. Missing dimensions cause layout shift, which is a Core Web Vitals failure on mobile — and mobile is what gets indexed.
12. Retired URLs return 410, verified
plokid avaldatakse
A removed page returns 410 Gone, confirmed by an actual request after deploy.
Miks?: A 404 lingers as a soft-404 for months; a 410 deindexes cleanly. And per-view dispatch often intercepts the request before the 410-returning view is ever reached, so the check has to be a real HTTP request, not a code read.
Miks see on linter ja mitte stiili juhend
Reegel, et ainult elab juhendamine on soovitus ~ mudel järgib seda enamasti aeg ja vaikselt ei ole ülejäänud, ja sa saad teada kolm kuud hiljem liiklusaruanne. Nii et need käivitada koodina, pärast lehekülg on kirjutatud ja enne seda läheb live. Lehekülg, mis ei blokeerimise reegel antakse tagasi põhjus ja ümber kirjutatud. Tulemus on kviitungil nii, et saate näha, mis kontrolli jooksis.
Ja midagi pole indekseeritud, kuni sa pole nii öelnud.
Iga sait algab noindex. Mitte vaikimisi sa pead avastama ~ reeglina linter jõustab, sest need saidid jagada domeeni ja üks halb naaber haiget kõigile. Kui saidi on väärt leidmist, lülitage indekseerimine sisse seaded ja see hakkab roomata.
Esimene vahetus tasuta