Ki sa anplwaye ou konnen anvan li bati nenpòt bagay

Nenpòt moun ka mete yon modèl sou yon sit entènèt. Sa yo se règleman li aplike a chak paj, poukisa chak youn egziste, ak ki moun nan yo anpeche yon pibliye pi vit pase avèti sou li.

Tout règleman ki anba yo te peye pou pa yon insidente sou yon sit nou kouri - yon ran de wòch, yon tradiksyon ki domaje, yon paj ki te fè li pwòp kòd sous li. Nou pa devine nan pi bon pratik; nou ekri anba sa ki deja te mal konsa li pa ale mal sou sit ou tou.

Règ ki bloke yon pibliye: 8 nan 12. Yon paj bloke se retounen nan anplwaye a ak rezon, epi li eseye ankò. Li pa pibliye epi avèti ou apre sa.

1. One page, one subject

Bloke

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

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

avèti

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

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

Bloke

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

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

Bloke

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

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

Bloke

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

Poukisa: 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 %}

Bloke

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

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

Bloke

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

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

Bloke

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

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

avèti

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

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

avèti

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

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

Bloke

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

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

Poukisa sa a se yon linter ak pa yon gid style

Yon règ ki sèlman viv nan yon enstriksyon se yon sijesyon - modèl la swiv li pifò tan an epi san yo pa fè rès la, epi ou jwenn deyò twa mwa pita nan yon rapò trafik. Se konsa, sa yo kouri kòm kòd, apre paj la se ekri ak anvan li ale nan lavi. Yon paj ki pa gen yon règleman blokaj se retounen ak rezon an ak re- ekri. Rezulte a se sou resi a nenpòt fason, konsa ou ka wè ki kalite tès ki te kouri.

Ak pa gen anyen ki endike jiskaske ou di sa

Pa default ou pa gen pou dekouvri — kòm yon règ linter la aplike, paske sit sa yo pataje yon domèn ak yon mal bòn zanmi fè mal tout moun sou li. Lè sit ou se vo jwenn, ou vire sou endèksman nan paramèt yo ak li kòmanse yo dwe crawled.

Rezilta linter pou chak paj se anrejistre sou resi li, ak resi yo disponib sou API.

Konpoze m 'yo konpayi gratis