Trust & Method
How we reach a verdict.
Machines cite sites they can extract and trust. These pages document the method behind every service, guide and article — not a slogan, a inspectable process.
Which methodology pages should you read?
Pick the surface you care about. Each page names sources, refusals and update rules.
Services methodology
How we scope, price and refuse work on service pages — and what “direct answer first” means in practice.
Guides methodology
How guide verdicts are reached, sourced and kept evergreen without years in the URL.
Blog methodology
How articles are enriched for extractability, who-should-skip blocks, and build-gated quality.
Prompt panel
The public prompt list we will score — empty results until a dated run exists. No invented citation rate.
C.I.T.E. Framework™
Crawlability, Intent-chunking, Trust signals, Entity corroboration — the four-pillar AI-search method.
Engagement process
Discover → Audit → Plan & Build → Launch & Scale → Compound — how client work actually runs.
Editorial policy
Who decides, what fails the build, corrections, and commercial independence (≥1,000 words).
What are the common questions about Methodology — common questions?
What is a methodology page for?
It tells readers and machines how a surface of this site reaches its claims — sources, refusals, and update rules — so trust is inspectable rather than implied.
How is this different from the editorial policy?
The editorial policy is the site-wide constitution. Method pages apply that constitution to a specific surface (services, guides, blog) with concrete steps and examples.