Apa yang pekerja awak tahu sebelum ia membina sesuatu

Sesiapa sahaja boleh menunjuk model ke laman web. Ini adalah peraturan yang ia gunakan pada setiap halaman, mengapa setiap satu wujud, dan mana yang menghentikan penerbitan berbanding memberi amaran tentangnya.

Setiap peraturan di bawah dibayar oleh insiden di laman web kami — tebing penarafan, terjemahan rosak, halaman yang mengembalikan kod sumbernya sendiri. Kami tidak meneka pada amalan terbaik; kami menulis apa yang telah berlaku salah supaya ia tidak berlaku salah di laman web anda juga.

Peraturan yang menghalang penerbitan secara langsung: 8 dari 12. Halaman yang dihalang akan diserahkan semula kepada pekerja dengan alasan, dan ia cuba lagi. Ia tidak menerbitkan dan memberi amaran kepada anda selepas itu.

1. One page, one subject

blok menerbitkan

Exactly one <h1>. A descriptive <title> of 15-60 characters.

Kenapa: 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

amaran

A meta description of 140-158 characters, unique to the page.

Kenapa: 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

blok menerbitkan

Every page gets body copy and FAQ answers written for that page. Never a shared template with a noun swapped in.

Kenapa: 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

blok menerbitkan

Every page self-canonicalises with an absolute URL. Any hreflang cluster ships alongside that canonical, also absolute.

Kenapa: 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

blok menerbitkan

Structured data mirrors the visible text exactly. Schema goes on the page types that earn a rich result, not on everything.

Kenapa: 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.

6. Django comments are {% comment %}

blok menerbitkan

Never {# #}. Not even on one line.

Kenapa: Django's template lexer regex has no DOTALL flag, so {# #} only closes on its own line. A multi-line one renders as visible page text, and if it contains a {% %} substring the lexer treats it as a real tag and every render crashes. Both have happened in production.

7. Positional {0} slots in translatable strings

blok menerbitkan

Any string that will be machine-translated uses {0}, {1} — never {name}.

Kenapa: 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

blok menerbitkan

Pages ship noindex. Indexing is a deliberate opt-in by the owner, per site.

Kenapa: 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

amaran

A page either does something useful or says something specific. A page that only describes a tool is not a page.

Kenapa: Thin wrappers around someone else's API are the clearest signal a quality classifier has. Real utility is what survives a core update.

11. Alt text and intrinsic dimensions on every image

amaran

Every <img> has alt text and explicit width/height.

Kenapa: 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

blok menerbitkan

A removed page returns 410 Gone, confirmed by an actual request after deploy.

Kenapa: 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.

Kenapa ini adalah linter dan bukan panduan gaya

Peraturan yang hanya hidup dalam arahan adalah cadangan - model mengikutinya kebanyakan masa dan diam- diam tidak melakukan selebihnya, dan anda dapati tiga bulan kemudian dalam laporan lalu lintas. Jadi ini berjalan sebagai kod, selepas halaman ditulis dan sebelum ia pergi hidup. Halaman yang gagal peraturan penghalang dipulangkan dengan sebab dan ditulis semula. Hasilnya adalah pada penerimaan sama ada cara, jadi anda boleh lihat periksa mana yang berjalan.

Dan tiada apa yang diindeks sehingga anda kata begitu

Setiap laman mula noindex. Bukan sebagai piawai anda perlu temui - sebagai peraturan linter memaksa, kerana laman ini berkongsi domain dan satu tetangga buruk merosakkan semua orang di dalamnya. Apabila laman anda bernilai dijumpai, anda matikan indeks dalam tetapan dan ia mula disorok.

Jalankan shift pertama anda bebas