What an editorial standards page is for, and what it is not
Someone deciding whether to rely on a page asks three quiet questions: who made this, how, and why. Google's guidance on helpful, people-first content suggests that site owners think about exactly those questions, and the AI-assisted content guide treats the byline as the answer to the first. The E-E-A-T guide adds the view across a whole site. It reports that Google's Search Quality Evaluator Guidelines rank trust above the other three qualities, and that being inaccurate can make a page untrustworthy however much experience, expertise and authority it shows. Among the practices it lists are, across the site, an about page, author pages and published editorial standards that explain how pieces are researched, checked and corrected, and, on each page, transparency about who runs the site and how it makes money.
Several guides on this site point their own decisions at that page. The AI-assisted content guide says the policy on disclosing AI belongs in the organisation's editorial standards. The tutorial on interviewing a subject-matter expert says the same of how interview-based pieces were produced. The product reviews guide notes that publishers who never let commercial considerations decide what is included or how it ranks write that into their standards. And the guide to correcting and updating published content recommends publishing a corrections policy. This tutorial writes the page all of those decisions land on. The editorial standardsThe rules for how content is made and kept honest: who writes and reviews it, how claims are sourced, how it is funded, where AI helps and how it is corrected. are the rules themselves; the page is the version readers can see and check.
The page is easier to write once it is clear what it is not. It is not the internal rulebook, and trying to make it one produces a document readers skip and writers ignore.
| Document | Written for | Question it settles | Read more in |
|---|---|---|---|
| Editorial standards page | Readers | How is content here made, checked, paid for and corrected? | This tutorial |
| Editorial style guideThe house rules a writer checks while drafting, so spelling, names, numbers, formatting, links and sources are handled the same way by everyone. | Writers | Which spellings, names, formats, links and sources do we use? | Writing an editorial style guide |
| Standards, roles and approvals | The content team | Who decides and approves, and to what standard? | Content governance |
| Outbound link policy | Writers, editors and the commercial team | Which links, which attributes, and what is never accepted? | Outbound links and link attributes |
| AI use policyA team's written rules for AI: approved tools, what each use may do, what data may go in, what is reviewed, when customers are told and who owns problems. | The team | Which tools and uses, what data, what review? | Writing a marketing AI use policy |
| Per-page disclosure | The reader of that page | What commercial relationship affects what I am reading? | Writing product reviews and roundups |
The internal documents hold the detail. The standards page states, in plain words, what those documents commit the team to, and links to the parts readers can use. It is not a legal notice either: terms of use, privacy notices and any wording a regulator expects in your markets belong with your adviser and the guidance the regulator publishes, and nothing here is legal advice.
Before you start
- Governance roles settled. Settle who owns the standards and who signs pages off before drafting. The content governance guide names the roles to start from: editor, subject reviewer, approver, publisher, content owner and governance owner. A RACI matrix with exactly one accountable role per row then settles who owns each routine the page will describe.
- The internal documents. Gather the style guide, the AI use policy and the AI use register, the outbound link policy, the contributor guidelines if you accept guest pieces, the method used for reviews, and the change record kept in the content inventory.
- A list of how the site earns. Every route by which money, products or services reach the business from what it publishes: its own products, affiliate programmes, sponsored placements, gifted or lent products, advertising.
- A recent sample of pages. A handful of pieces from the last few months, including a review, a contribution and a correction if you have them, to test each statement against.
- A reader from outside the team. Someone who does not write for you, to read the draft and say where it is vague or sounds like marketing copy.
The steps
The steps run in order. The first decides what the page is allowed to say; the middle ones write one section each; the last two place the page where readers will find it and keep it honest.
List the routines the team already runs and who owns each
Write down, as plainly as you can, what actually happens to a piece between the idea and the reader: who drafts it, who checks the facts and against what, who approves it, how products for reviews are obtained, what happens to affiliate links, where AI tools are used, and what happens when someone reports an error. Give each routine one accountable owner in the RACI matrix. Then mark each routine honestly as kept every time, kept sometimes, or written down but not kept. Only the first group goes on the page as it stands. For the others, decide now: fix the routine before publishing, or leave it off. A standards page that describes the routine you would like to run is a page a reader can catch out, and the first reader who does will doubt everything else on it.
Decide who the page is for and where it lives
Write for the reader who has just arrived from a search result or a newsletter and wants to know whether to rely on what they read. That reader does not know your job titles, tools or internal names, so describe roles by what they do. Give the page one stable address and one plain name, such as "How we write and check our content", and keep it in one place rather than scattered across an about page, a footer note and a separate review policy. If the site publishes different kinds of content, such as guides, reviews and news, use one page with a section for each rather than several pages that drift apart.
Say who writes, who reviews and how authors are credited
Say who writes: staff, freelance writers, outside contributors, customers telling their own stories. Say that every piece carries a real person's name, and what a bylineThe name a published article is credited to: the person whose expertise it claims and who answers for it, agreed with writers, experts and contributors. means on your site, because, as the AI disclosure guide puts it, a byline claims authorship. If writers draft from interviews with experts, say how the credit works, following the byline table in the interviewing tutorial; if freelancers write under their own names or under yours, say which, as agreed in the guide to working with freelance writers. Say which pages get a subject review and from whom, and that the reviewer is named and the review dated where a reader who acts on a mistake could be harmed, as the E-E-A-T guide describes for high-stakes topics. Link the author pages; whether their archives are indexed is a separate decision the index rules for archive pages settle.
Describe how pieces are researched and which sources come first
Readers want to know what stands behind a claim. Take the sourcing rule from the house style guide, which borrows it from the outbound links guide: link the original source rather than a page that passes the claim on, put each citation beside the claim it supports, and prefer primary sources and official documentation to summaries. Say how first-hand experience is used and labelled, because a test you ran yourself is evidence of a different kind from a study you cite. The hierarchy of evidence is a useful way to shape this section: say which kinds of claim the site makes on which kinds of evidence, that opinion is labelled as opinion, and that a claim nobody can source is rewritten or removed. If you publish reviews, link the method page the product reviews guide asks for rather than describing the method twice.
Say how the site makes money and how each page tells readers
List every way the business earns from what it publishes, in words an ordinary reader understands: we sell our own products, we earn a commission when you buy through some links, some articles are paid placements, some products reach us free or on loan. Then say what each page does about it. The influencer contracts and disclosure guide reads the FTC's endorsement guidance as expecting a material connectionA relationship between an endorser and a brand, such as a fee, free product, commission or employment, that endorsement guidance expects to be disclosed. to be made clear and conspicuous to readers, with gifts and affiliate links among the connections it covers. The media and publishing guide records that, under the UK advertising codes the ASA administers, marketing must be obviously identifiable, and that affiliate links in reviews, branded content and advertorials all count as advertising. The product reviews guide adds the point this page must not undermine: a disclosure belongs near the top of the page and again where the links are, and a footer link to a disclosure page, on its own, is not where readers meet it. So the standards page explains the policy, and every affected page still carries its own line. Say too that paid and affiliate links are marked as sponsored, as the outbound links guide sets out, and, only if it is true, that no commercial relationship decides what is included or how it ranks. How labels are worded is for your adviser and each market's regulator guidance to settle.
State how AI is and is not used, and who checks it
Take this section from the AI use policy and its register of uses, not from memory. Say at which stages AI tools help, such as research summaries, outlines, first drafts or alternative text, which stages they never touch, and that a named person checks and edits the result before anything is published: the human reviewThe step where a named person checks AI-assisted work for accuracy, sources, originality, privacy and disclosure before it is published or sent. the AI-assisted content guide treats as a gate nothing bypasses. Say when readers are told. The AI disclosure guide's test is whether a reasonable person would feel misled on learning how something was made, and Google's guidance, as the AI-assisted content guide reports it, suggests telling readers how a piece was produced when they would reasonably expect to know. Keep the section consistent with the short public statement that the guide on customer questions about AI use prepares from the same register, and never write "we do not use AI" to reassure: an untrue denial is a statement by the business, and tools built into everyday software count as use.
Set out updates, corrections and how readers report an error
This section is the corrections policy the updating and correcting guide describes. Say what the published date and the updated date mean on your pages, and that the published date never moves. Say how a substantive update is marked and how errors are put right: openly, with a dated note that names the error and gives the corrected version, and in the places where readers met the wrong version where that is practical. Say what happens to a page that cannot be made accurate, following that guide's withdrawal rules and the SOP for removing a web page. Then give readers a way to report an error that reaches a named owner, and say, in your own words, how soon someone looks at a report, promising only what the team really manages, because a promise of speed that is missed is itself a correction the page will need.
Cover contributors, sponsored pieces and reviews
If outside writers contribute, say that their pieces are edited to the same standards as staff work, carry the contributor's real name and an author page, and disclose any commercial connection to what the piece mentions, as the guide to accepting guest contributions describes; link the contributor guidelines. If the site sells sponsored placements, say how they are labelled, who edits them and that their commercial links are qualified; the sponsored articles guide covers the same arrangement from the buyer's side. If you publish customer stories, say that customers agree in writing to what is published and that any incentive is disclosed, as the customer case study tutorial requires. Each of these is a sentence or two and a link; the detail stays in the document behind it.
Link the page from where readers will look for it
Readers rarely go looking for a standards page from the home page. They reach it with a question about a specific page, so put the link where that question arises: the site footer and the about page, every author page, the disclosure line on reviews and pages with affiliate links, every correction note, as the corrections guide recommends, and the contributor guidelines. Link out from the standards page to the author pages, the review method, the contributor guidelines and the route for reporting errors, so that a reader can check each promise in a click or two. Keep every per-page disclosure in place; the link to the standards page sits beside it, not instead of it.
Date it, name an owner and check it against practice
Show the date the page was last revised and keep a short change history at its foot, so that a returning reader can see what changed and when. Give it one owner, usually the governance owner, who is told whenever a routine it describes changes and updates the page before the change takes effect. Then check it against practice on a rhythm written into the governance calendar: take a sample of recent pages and test each promise against them. Are the bylines real names with author pages? Are claims cited where they are made? Does every review and affiliate page carry its disclosure line? Were the corrections in the inventory's change record made openly? Where practice has slipped, fix the practice first; where the page promised more than the team does, change the page. Never leave the two apart. The content strategy hub gathers the style guide, governance and corrections routines this page summarises.
What each section says and the routine behind it
Each section of the page summarises something the team already does. The table pairs them, with the overreach that most often creeps in when a page is written from aspiration rather than practice.
| Section | What it tells readers | The routine or document behind it | Overreach to avoid |
|---|---|---|---|
| Who we are and what we cover | The site's purpose and the subjects it covers | The content strategy and its pillars | Claiming expertise in subjects the site rarely covers |
| Who writes and reviews | Real authors, who reviews what, how credit works | Governance roles, author pages, byline agreements | "Every article is expert-reviewed" when only some are |
| Research and sources | Which sources come first and where citations sit | The style guide's sourcing rule, the outbound link policy | "All facts are independently verified" with no check that does it |
| How we make money | Every revenue route and how each page discloses it | The outbound link policy, the review method, sponsored terms | A standards page standing in for per-page labels |
| How we use AI | Where AI helps, where it does not, who checks it | The AI use policy and register | "We do not use AI" while built-in tools are in use |
| Updates and corrections | What dates mean, how corrections appear, how to report an error | The change record in the content inventory | A response time nobody tracks |
| Contributors and partners | How outside pieces are edited, credited, labelled and linked | Contributor guidelines, sponsored placement terms | Contributions published with less scrutiny than staff work |
A section with nothing to put in the third column is a section to leave out until the routine exists.
A stargazing guides site publishes its standards (illustrative)
Quvelmarsk Skies writes its standards from the routines it runs
Quvelmarsk Skies, an invented stargazing guides site, publishes 140 beginner guides, 36 telescope and binocular reviews with affiliate links, articles from 9 amateur astronomers and a monthly sky calendar whose first draft comes from an AI tool. A reader emails to ask whether the reviewed telescopes were free and who checks the calendar's dates. The editor lists 12 routines and marks each honestly. Ten are kept every time. Two are not: in 3 of the last 12 months the calendar went out without a named person checking every date against the almanac the site uses, and 4 of last year's 11 corrected errors were fixed silently. She fixes both before writing a word, naming a checker for each calendar and logging every correction as a dated note on the page. The finished standards page runs to about 900 words in 7 sections. It says that 31 of the 36 reviewed models were bought by the site and 5 were lent by their makers and returned, that affiliate links earn a commission and are marked on every review, that the calendar is drafted with AI and checked line by line by a named member of the team, and how to report an error. It is linked from the footer, all 14 author pages, every review's disclosure line and every correction note. At the first quarterly check, a sample of 10 recent pages finds one review whose comparison table carried affiliate links without the disclosure line beside it; the line is added and the review template changed so the table cannot be published without it.
Common mistakes
- Describing the routine you want rather than the one you run. Every sentence is a promise a reader can test; fix the routine or leave the sentence out.
- A standards page in place of per-page disclosure. Readers meet commercial relationships on the page they are reading, not in the footer. Keep each page's own line and link the standards page beside it.
- Copying another publisher's standards. Their routines are not yours, and borrowed promises are broken from the day they go live.
- Publishing the internal documents as the page. A reader does not need the style guide or the AI register; they need what those documents commit the team to, in plain words.
- Promising speed nobody tracks. A response time for error reports that is routinely missed turns the corrections section into a broken promise.
- Hiding how the site earns. A vague line about "partners" tells readers less than a plain list of commission links, paid placements and gifted products.
- "We do not use AI" as reassurance. If any tool in the workflow uses it, the denial is untrue, and readers who find out stop trusting the rest of the page.
- Publishing it once and walking away. Routines change, people leave and new ways of earning arrive; a page with no owner, no date and no check soon describes a team that no longer exists.
