Gixo Quill · content guide
Technical SEO
Technical SEO is everything that determines whether a search engine can crawl, render, index and understand your pages. It rarely makes mediocre content rank — but technical failures routinely stop good content ranking at all, which is why it is checked first.
What your plan includes. Writing, checks, exports, public share links, publishing to WordPress and Ghost, and the Medium export are on every plan, from $10 per seat a month. Brand Voice needs Starter; comments and Brand Kit need Professional; bulk needs Business.
What it covers, roughly in order of consequence
- Indexability. Robots directives, noindex tags, canonical tags. A wrong canonical or a stray noindex removes a page entirely — the highest-consequence failure and the easiest to miss.
- Crawlability. Internal linking, sitemaps and crawl budget. A page nothing links to is a page that gets found late or not at all.
- Rendering. Whether content exists without JavaScript execution. Client-rendered content is crawled less reliably than server-rendered.
- Duplication. The same content on several URLs splits signals. Parameters, trailing slashes and host variants are the usual culprits.
- Structured data. Schema that helps engines understand what a page is, and increasingly what to quote from it.
- Core Web Vitals. Real, but a tiebreaker. Fixing them will not rescue a page that is not indexed.
Where to look first when something is not ranking
| Symptom | Usual cause | Where to check |
|---|---|---|
| Page not in the index | Inspect indexing, canonical selection and crawl access | Search Console URL inspection |
| Indexed but no impressions | Review demand, relevance and the specific search feature | Query data, snippet eligibility and comparison pages |
| Wrong page ranking | Duplication or cannibalisation | Site search for the query |
| Crawled late or never | No internal links pointing to it | Internal link report |
| Rich result not showing | Check support, eligibility and markup; display is not guaranteed | Current Google documentation and the published page |
How Gixo Quill handles this
Quill contributes a structured HTML body and deterministic content checks. It builds Article JSON-LD and FAQPage JSON-LD for articles with a visible FAQ section, and Product/Offer markup from supplied product-description fields. HowTo markup remains a receiving-CMS task. Review the destination's visible content and markup together; rendering, sitemaps, canonicals and crawling remain site-level responsibilities.
Frequently asked questions
What is technical SEO?
Everything determining whether a search engine can crawl, render, index and understand your pages — indexability, crawlability, rendering, duplication, structured data and performance.
What matters most in technical SEO?
Indexability. A wrong canonical tag or a stray noindex removes a page from search entirely, which outweighs every performance optimisation you could make.
Do Core Web Vitals affect rankings?
They are a genuine but modest factor, best understood as a tiebreaker between comparable pages. They will not rescue a page that is not indexed or does not match intent.
How often should I run a technical audit?
A full audit a couple of times a year, plus checks after any platform migration, template change or URL structure change — which is when most technical damage actually happens.
Is technical SEO enough to rank?
No. It removes obstacles rather than creating demand. Technical work makes good content rankable; it does not make weak content rank.
Related content guides
Start with structured content, then finish technical SEO in the CMS
Quill produces a structured body and can check supplied JSON-LD; the receiving platform remains responsible for rendering, metadata, generic schema, canonicals, sitemaps and crawlability.
Inside Quill
Review concrete content and SEO signals before delivery
Updated