Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Standard Operating Procedures

Publishing a Web Page SOP

A standard procedure for publishing a web page: final copy checks, metadata, schema, internal links, tracking, publishing, indexing request and hand-off.
SOPbeginner7 min readUpdated

Owner, trigger and scope

The web publisher owns this procedure and runs it end to end. The SEO lead owns the standards it checks against, answers questions at the metadata and structured data steps, and signs off the QA checks. On a small team one person may hold both roles; in that case the QA checks should still be run as a separate pass after a break, because the person who built the page reads what they meant rather than what is there.

The trigger is any new page, or any existing page whose title, URL, main heading, topic or template has changed. Blog posts, landing pages, product pages and help articles are all in scope. Minor copy fixes are out of scope but still logged at the final step. When the change is a new address for a page that is already live, run the SOP for changing a page URL around this one: it adds the redirect, the old address's links in every channel and the checks afterwards.

The SOP covers the work from an approved draft to a page that is live, linked, tracked and submitted for indexing. It does not cover writing or editing the copy, keyword research, design, or anything about the page's performance after launch; those belong to content planning and to ongoing SEO work.

The templates these pages are published on are specified separately, before they are built, as described in writing SEO requirements for developers.

Before you start: inputs and access

Have the following open before step one, or stop and ask for them:

InputWhere it comes fromWhy it matters
Approved draftEditor or content ownerNothing unapproved goes live
Target URL and primary topicContent brief or SEO leadDrives the slug, title and canonical
Title and meta description draftWriter or SEO leadAvoids writing metadata under time pressure
Structured data type, if anySEO leadKeeps markup consistent across templates
Internal link targetsSEO lead or content mapConnects the page into its cluster
Analytics and tag accessAnalytics ownerLets you confirm tracking on the live page
Search Console accessSEO leadNeeded for the indexing request

You need publisher rights in the CMS, preview access on a staging or draft URL, and at least restricted access to the Search Console property. Open the SEO page publishing checklist in another tab; you will run it at the QA step.

The procedure

  1. Confirm approval and freeze the copy

    Check that the draft carries a recorded approval from its owner, with a date, and that nobody is still editing it. Copy the final text into the CMS from the approved version only, never from an earlier draft or an email thread. If the copy changes after this point, the page goes back to its approver before you continue. Freezing the copy here is what makes every later check meaningful.

  2. Set the URL, title and meta description

    Set the slug agreed in the brief, then enter the title tag and meta description. Follow the house rules in the guide to title tags and meta descriptions rather than improvising: one primary topic per title, a description that summarises the page honestly, and no duplication of another live page. Set the main heading separately if your CMS allows it, and add alt text to every meaningful image.

  3. Add structured data and the canonical

    Apply the structured data type the SEO lead specified, using the template's built-in fields where they exist. The structured data guide explains which types suit which pages; this step only applies the decision. Then confirm the Canonical Tag points to the page's own final URL, unless the brief says it is a variant of another page. Validate the Schema Markup in a testing tool on the preview URL before moving on.

  4. Add internal links in both directions

    Add the outbound links the brief lists, with descriptive anchors that tell a reader where they will land. Then add inbound links: edit at least one relevant hub or related page so the new page is reachable from the existing site, not just from the sitemap. The internal linking guide covers anchor choice and cluster structure. Record which pages you edited, because they are part of this change.

  5. Check tracking on the preview

    Open the preview URL with your tag debugger and confirm the page view fires and any forms, buttons or downloads on the page trigger the events the tracking plan expects. Check that the consent banner behaves as it does elsewhere on the site. If the page introduces a new form or a new type of conversion, stop and ask the analytics owner before publishing, because an untracked conversion page is expensive to fix later.

  6. Publish and check the live page

    Publish, then open the live URL in a private window on desktop and on a phone. Confirm it returns a normal response rather than a redirect, that the page is not set to noindex, and that the title, description and canonical in the page source match what you entered. Check headings, images and links render correctly and that the page is readable with keyboard navigation, in line with the accessibility guidance in WCAG.

  7. Request indexing and update the sitemap

    Confirm the page appears in the XML sitemap, or add it if your CMS does not do so automatically. In GSC, inspect the live URL and request indexing if the page is commercially important or time-sensitive. The help centre describes this as a request, not a guarantee, so do not repeat it daily; check the URL inspection again after a few days instead.

  8. Log the change

    Add a line to the publishing log with the URL, the date, the publisher, the approver, the pages edited for internal links and whether indexing was requested. Note any deviation from this SOP and why. The log is how the SEO lead later connects a traffic change to a publication, and how anyone can see what changed on a page without guessing.

Illustrative example — not a real result

A software company publishing a comparison page

Cobaltstile Analytics, an invented reporting software company, publishes a new comparison page on a Tuesday. The publisher sets the title and description from the brief, adds Product and FAQ markup, and edits 3 existing pages to link to the new one. At the QA step the SEO lead finds the canonical still points to the draft address on the staging domain, a fault inherited from the template. It is fixed before the indexing request. Search Console shows the page indexed 4 days later, and the publishing log entry lets the team match the first 120 organic clicks in its opening fortnight to the right publication date.

QA checks

Run these as a separate pass before sign-off, ideally by the SEO lead rather than the publisher:

  • Copy matches the approved version, with no leftover placeholder text or tracked changes.
  • Title and description are present, unique on the site and match the brief's topic.
  • Main heading is present once and matches the page's purpose.
  • Canonical points to the final live URL, or to the agreed primary version.
  • Indexing is allowed: no noindex tag and no robots block on the live URL.
  • Structured data validates on the live URL, not just on the preview.
  • Internal links exist both to and from the page, with descriptive anchors.
  • Images carry alt text and load quickly on a phone.
  • Tracking records a page view and the page's key interactions.
  • Accessibility basics pass: headings in order, readable contrast, usable by keyboard.
  • Checklist run complete: every item on the publishing checklist is ticked or has a noted exception.

Hand-offs and records

When the QA checks pass, the publisher hands the live URL and the log entry to the SEO lead, who becomes responsible for monitoring the page's indexing and early search performance. If the page is a campaign landing page, the publisher also tells the campaign manager that the URL is live so that ads or emails can point to it; the campaign manager should not need to discover this from the CMS.

The records this SOP leaves behind are the approval note on the draft, the publishing log entry, the list of pages edited for internal links, and the indexing request recorded in Search Console. Keep the log in one shared place, not in individual inboxes. If any QA check failed and was knowingly accepted, record the exception and the person who accepted it, so the issue can be picked up later rather than forgotten.

Common mistakes

  • Publishing from the wrong draft. Pasting from an old version reintroduces copy the approver removed. Always copy from the approved version.
  • Writing metadata at the last minute. Titles written under pressure duplicate other pages or miss the topic. Draft them with the copy.
  • Orphan pages. A page linked only from the sitemap is hard to discover. Edit at least one existing page to link to it.
  • Leaving a staging noindex in place. Templates copied from staging often carry a noindex. Check the live source, not the CMS setting.
  • Canonical pointing at the preview URL. Some CMSs fill the canonical from the draft address. Check it after publishing.
  • Requesting indexing repeatedly. Repeat requests do not speed anything up. Request once, then inspect later.
  • Not logging small changes. Untracked edits make later traffic changes impossible to explain.

Frequently asked questions

Who should own the publishing SOP, the writer or the SEO lead?

The web publisher owns the procedure because they control the CMS and the moment a page goes live. The SEO lead owns the standards the procedure checks against and signs off the QA step, so the two roles divide doing from approving.

Do I need to request indexing for every page I publish?

No. Search engines discover most pages through links and sitemaps, and the Search Console help documents indexing requests as a way to ask for a crawl, not a guarantee. Requesting indexing is worth doing for pages that matter commercially or are time-sensitive, and harmless for the rest.

What counts as a substantially changed page that should go through the SOP again?

A change to the title, the URL, the main heading, the primary topic or the template counts, as does adding or removing structured data. A typo fix or a refreshed image usually does not, though it is still worth logging so the change history stays complete.

Terms used on this page

Where this page is used

Also related

Sources

  1. SEO Starter Guide — Google Search Central
  2. Web Content Accessibility Guidelines (WCAG) — W3C

Related