Apa sing ditetepake karyawan sadurunge ngawangun apa wae
Saha waé bisa nyarankeun model ka situs wéb. Ieu aturan anu diterapkeun ka unggal halaman, naha unggal halaman aya, sarta naon anu nyababkeun henteuna publikasi tibatan ngawartosan ngeunaan éta.
Satiap aturan di handap ieu ditanggung ku hiji kajadian dina situs anu urang jalankeun - hiji jurang ranking, hiji terjemahan rusak, hiji halaman anu ngahasilkeun kode sumberna sorangan. Kami henteu nyatet dina praktek anu pangsaéna; kami nuliskeun naon anu parantos salah supados henteu salah dina situs anjeun ogé.
Aturan kang ngblokir publikasi langsung: 8 of 12. Halaman anu diblokir dipulangkeun ka pagawé kalayan alesan, sarta dicoba deui. Éta henteu diterbitkeun sareng ngawartosan anjeun saatosna.
1. One page, one subject
blocks publish
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
warta
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
blocks publish
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
blocks publish
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
blocks publish
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.
7. Positional {0} slots in translatable strings
blocks publish
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
blocks publish
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
warta
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.
10. No orphans
warta
Every indexable page has at least one inbound internal link.
Kenapa: 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
warta
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
blocks publish
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.
Mengapa ini adalah linter dan bukan panduan gaya
Aturan anu ngan hirup dina instruksi nyaéta saran - model ngalaksanakeunana saeutik-eutik sawaktu-waktu sarta teu ngalaksanakeunana sacara diam-diam, sarta anjeun manggihanna tilu bulan saterusna dina laporan lalulintas. Jadi ieu dijalankeun salaku kode, sanggeus halaman ditulis sarta saméméh éta dilaksanakeun. Halaman anu gagal dina aturan blok dipulangkeun kalayan alesanna sarta ditulis deui. Hasilna aya dina konfirmasi, ku kituna anjeun tiasa ningali mana checks anu dijalankeun.
Lan ora ana sing diindeks nganti sampeyan ngandika
Satiap situs ngamimitian noindex. Teu kawas piawai anjeun kudu manggihan - salaku aturan linter enforces, sabab situs ieu babagi domain jeung hiji batur jahat ngarugikeun saha waé dina eta. Lamun situs anjeun patut dipanggihan, anjeun ngahurungkeun indeksing dina pangaturan sarta eta dimimitian ku dicrawled.
Hasil linter kanggo saben kaca dicatat ing resi, lan resi ana liwat API.
Nggawe perusahaanku gratis