Editorial principles
The standards behind every Growthract article.
Useful before impressive
Content should help the reader understand a problem, evaluate an option or make a better decision. We do not add complexity simply to make an article appear more authoritative.
Evidence before certainty
Search systems change frequently. We distinguish documented facts, practical observations, informed analysis and illustrative scenarios instead of presenting every statement as settled fact.
Clarity before volume
We would rather publish a focused explanation than expand an article with repetitive sections created only to increase its length.
Transparency before promotion
Examples, limitations, commercial relationships and illustrative results should be described clearly enough for readers to understand what they represent.
Research and review
How Growthract researches and reviews content.
Our process begins with the reader’s question and works outward through primary information, credible supporting research and practical experience.
Define the reader and question
Before drafting, we identify who the content is for, what they are trying to understand and what decision the article should help them make.
Review primary information
Where possible, we begin with official documentation, platform guidance, standards, product documentation and original research rather than relying entirely on secondary commentary.
Compare credible sources
Important or uncertain claims are compared across relevant sources. Differences, limitations and areas without clear consensus are considered during drafting.
Connect research to practice
Research is evaluated against practical SEO, content, analytics and search-visibility experience so recommendations remain useful in real operating environments.
Review structure and accuracy
Before publication, content is reviewed for factual consistency, logical flow, unsupported certainty, misleading language and unnecessary repetition.
Publish with clear context
The final page should identify its author, publication context and whether examples or case-study outcomes are real, modeled or illustrative.
Original research standard
Published research should be inspectable, qualified and reproducible.
When Growthract publishes original datasets or benchmarks, we document what was measured, how the sample was defined, which observations were unavailable or unknown, and the limitations readers should consider before interpreting the results.
Frozen scope
The sample, collection rules and observation period are defined before results are presented.
Observable evidence
Findings distinguish direct public observations from interpretation, inference and platform claims.
Explicit denominators
Percentages identify the population actually measured when unavailable or unknown observations affect the denominator.
No causal shortcuts
Observed technical patterns are not presented as proof that a signal causes rankings, citations or AI recommendations.
The 2026 AI Search Readiness Benchmark follows this approach and publishes its supporting aggregate data, company-level observations, page-level observations and methodology notes.
Review the benchmarkVerification
How claims and examples are verified.
The level of verification should reflect the importance and specificity of the claim. We avoid presenting assumptions, predictions or modeled examples as verified outcomes.
Platform and technical claims
Claims about Google, ChatGPT, Perplexity, Claude, Gemini and other platforms should be grounded in official documentation, observable product behavior or clearly attributed third-party research.
Performance claims
Traffic, ranking, revenue, citation and conversion results should only be presented as real outcomes when supporting evidence exists and the context needed to interpret the result can be provided.
Examples and calculations
Modeled examples should explain their assumptions. Percentages should include the baseline and resulting value when that context materially changes how the number is understood.
Predictions and interpretations
Forward-looking statements and strategic interpretations are presented as analysis, not guaranteed outcomes.
Third-party references
External sources are selected for relevance and credibility. Linking to a source does not mean Growthract endorses every claim or position published by that source.
Illustrative case studies
How illustrative scenarios are labelled.
Illustrative case studies demonstrate how a strategy could be applied without claiming that the scenario represents verified client work.
Our labelling requirements
The page is visibly labelled “Illustrative Case Study.”
The introduction explains that the scenario is modeled rather than presented as verified client work.
Invented company names, testimonials or client identities are not used to imply real engagement.
Modeled metrics explain their baseline, calculation and intended meaning.
Outcomes are framed as what the strategy could produce or what improvement would look like.
Illustrative examples are not included in claims about Growthract’s verified client results.
Article maintenance
How articles are reviewed and updated.
Search platforms and recommended practices change. Published content should be reviewed when new information could materially affect its usefulness or accuracy.
A platform changes its official guidance or documented behavior.
A recommendation is no longer accurate or useful.
New evidence materially changes the article’s conclusion.
A cited source becomes unavailable or is substantially revised.
A reader identifies an error, ambiguity or missing qualification.
Growthract’s process, product or service changes.
When an article receives a material review, its visible “last updated” date and structured data should reflect the review date. Minor formatting changes do not justify presenting an article as newly updated.
Corrections
How corrections are handled.
Readers should be able to report a potential error or misleading statement. Corrections are evaluated on their substance, not on whether they make the original article appear less polished.
Review the report
We compare the reported issue with the page, its supporting sources and the context in which the statement appears.
Correct material errors
When a factual error or misleading statement is confirmed, we update the content rather than preserving it for the sake of consistency.
Clarify ambiguous language
If a statement is technically defensible but likely to create the wrong impression, we revise it for clarity.
Preserve honest context
Corrections should not remove qualifications, limitations or evidence simply because they make a claim less promotional.
Report a correction
Found something that needs review?
Include the page URL, the statement you believe needs review and any relevant supporting source.
Email hello@growthract.com