Mutable facts
Anything that changes, prices, product limits, policies, market data, incidents, should cite a primary source and say when we checked it and which region, plan currency, or version.
How we publish
Editorial &
evidence policy.
We try to make it obvious which is which: a fact from someone else, something we saw ourselves, an estimate, an opinion, or a commercial term.
Effective
Last reviewed
01 / The standards
Publication controls
First-party results
Case-study results should identify the project, source record, dates, sample, tools, metric definitions, method and limitations. Before-and-after comparisons should use comparable conditions, and client or data-owner permission should be recorded before publication. Results are not presented as typical or guaranteed.
Estimates and illustrations
Forecasts, example budgets and calculators are labelled as estimates, state what they assume, and are never presented as quotes or promises.
Search and performance
Lab tests are distinguished from field data. Search rankings, indexing, traffic, AI citations, PageSpeed scores under all conditions, conversions, and revenue are not guaranteed.
Comparisons
When we compare named companies we say how we picked them, where the information came from, when we checked, where the scope genuinely differs, and what PandaCodeGen's commercial interest in the comparison is.
Corrections
Material errors are corrected in the page and its metadata. A correction note should be added when the change affects the conclusion or a reader's commercial decision.
02 / Keeping information current
Review and freshness
High-volatility pages, including price trackers, product changes, incidents, legal or privacy topics, and current-year comparisons, require a primary-source check before publication and a scheduled recheck. Evergreen technical guidance is reviewed when a relevant platform, standard, or source changes.
A visible date does not prove that every fact on a page is current.
03 / Release review
Content review status
The July 2026 release review covered every current blog route and its shared search-card and FAQ data. Universal ranking, revenue, performance, hosting, cutover, ownership, refund, and AI-citation promises were removed or bounded, and a repository release gate now checks those prohibited patterns.
Mutable vendor, product, price, incident, market, security, and legal facts still require a dated primary-source check whenever an article is materially updated. Readers should never treat an example as a PandaCodeGen quote, guarantee, or prediction for their project.
04 / People and AI assistance
How this content is produced
Articles on this site are researched, drafted and edited by a named person with AI assistance, and every one carries a byline that resolves to that person's background page. AI tools are used the way a research assistant and a copy editor are used: to gather candidate sources, draft and restructure passages, and check prose for clarity. They are not used to publish unreviewed output, and no article is generated and posted without a human reading it in full.
Every factual claim, price, date, limit and quotation is verified against the primary source by a person before publication, and the date of that check is written into the page rather than implied by the timestamp. Where a figure cannot be verified against a primary source, we say so and leave it out rather than repeat it from a secondary summary.
Where we publish an observation of our own, it carries the method and the date so a reader can repeat it. We disclose this because we recommend readers ask vendors the same question, and it would be inconsistent to ask it without answering it here.
05 / Open to correction
Report a correction
Send the page URL, disputed statement, and supporting primary source to:
info@pandacodegen.comWe review corrections on their evidence, regardless of whether the sender is a customer, competitor, vendor, or reader.