Zer da zure langileak ezer eraiki aurretik dakiena
Edonork webgune batean eredu bat jarri dezake. Hauek dira orrialde bakoitzari aplikatzen dizkion arauak, zergatik dagoen bakoitza eta zeinek gelditzen duen argitaratzea, horren berri eman beharrean.
Atal honetan azaltzen diren arau bakoitzak gure webguneetako gertaera batek ordaindu du - rankingeko amildegi bat, itzulpen hautsi bat, bere iturburu kodea errendatu zuen orri bat. Ez gara praktika onenak asmatzen ari; jadanik okertu zena idazten ari gara, zure webgunean ere okertu ez dadin.
Argitaratzea zuzenean blokeatzen duten arauak: 8 edo 12. Blokeatutako orrialde bat langileari arrazoiarekin itzultzen zaio, eta berriro saiatzen da. Ez du argitaratzen eta ondoren ohartarazten zaitu.
1. One page, one subject
blokeak argitaratzen
Exactly one <h1>. A descriptive <title> of 15-60 characters.
Zergatik: 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
abisua
A meta description of 140-158 characters, unique to the page.
Zergatik: 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
blokeak argitaratzen
Every page gets body copy and FAQ answers written for that page. Never a shared template with a noun swapped in.
Zergatik: 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
blokeak argitaratzen
Every page self-canonicalises with an absolute URL. Any hreflang cluster ships alongside that canonical, also absolute.
Zergatik: 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
blokeak argitaratzen
Structured data mirrors the visible text exactly. Schema goes on the page types that earn a rich result, not on everything.
Zergatik: 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
blokeak argitaratzen
Any string that will be machine-translated uses {0}, {1} — never {name}.
Zergatik: 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
blokeak argitaratzen
Pages ship noindex. Indexing is a deliberate opt-in by the owner, per site.
Zergatik: 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
abisua
A page either does something useful or says something specific. A page that only describes a tool is not a page.
Zergatik: 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
abisua
Every indexable page has at least one inbound internal link.
Zergatik: 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
abisua
Every <img> has alt text and explicit width/height.
Zergatik: 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
blokeak argitaratzen
A removed page returns 410 Gone, confirmed by an actual request after deploy.
Zergatik: 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.
Zergatik da hau linter bat eta ez estilo-gida bat
Agindu batean bakarrik bizi den arau bat iradokizun bat da - ereduak denbora gehienean jarraitzen du eta isiltasunean ez du gainerakoa jarraitzen, eta hiru hilabete geroago trafiko txosten batean jakingo duzu. Beraz, kode gisa exekutatzen dira, orrialdea idatzi ondoren eta bizian jarri aurretik. Blokeatzeko arau batek huts egiten duen orrialde bat arrazoiarekin itzultzen da eta biridazten da. Emaitza jasota dago, nolanahi ere, zein egiaztapen exekutatu diren ikusi ahal izateko.
Eta ezer ez da indexatuko zuk hala esaten duzun arte
Gune bakoitzak noindex-a hasten du. Ez da lehenetsia aurkitu behar duzula, baina linter-ak arau gisa inposatzen du, gune hauek domeinu bat partekatzen dutelako eta auzokide txar batek bertan dauden guztiei kalte egiten dielako. Zure gunea aurkitzea merezi duenean, indexazioa ezarpenetan aktibatzen duzu eta arrastreatzen hasten da.
Orrialde bakoitzaren linter emaitza bere ordainagirian erregistratzen da, eta ordainagiriak eskuragarri daude APIaren gainetik.
Nire konpainia librea eraiki