Siteoscope

Contributor Program

Contribute practitioner-grade SEO and analytics writing.

The Siteoscope blog is a technical resource for SEO operators and marketing analytics practitioners. If you came here searching for “write for us SEO” or “guest post marketing analytics”, keep reading — we publish working practitioners, we pay attention to the craft, and we partner with an editor on every piece before it ships.

Who we publish

Operators, not placement specialists.

We publish people who have done the work. If the most interesting sentence in your pitch is about domain authority or link building, this is not the right home for that piece.

In-house SEO leads

Running the program at mid-market B2B companies. You have crawl budgets, rendering debates, and log files in your recent browser history.

Data engineers on attribution + analytics pipelines

You ship the joins behind GA4, Segment, warehouse models, and BI dashboards. You know where the data quietly breaks.

Marketing analytics consultants and freelancers

Independent operators who have shipped measurement work for real clients. Case studies welcome; NDAs respected.

Agency SEO directors with published case studies

You have led programs end to end and can write without having to pitch a tool at the end of every paragraph.

Former practitioners turned educators

Ex-operators who now teach, train, or run communities. Your opinions are earned, not sourced from a keyword brief.

Topics we publish

The territory we cover.

Pitches that sit cleanly inside one of these areas move faster. Cross-cutting angles are fine — a data-quality lens on attribution, for example — as long as the core is technical and the reader is a practitioner.

  • Technical SEO

    Log analysis, rendering edge cases, Core Web Vitals at scale, crawl budget, JS rendering parity, sitemap and canonical hygiene for large sites.

  • Rank tracking methodology

    SERP volatility, AI-overview impact on clicks, click-through modelling, tracking at the feature level (PAA, pack, knowledge panel).

  • Data quality in the marketing stack

    GA4 pitfalls, Segment schema governance, server-side tagging, identity stitching, attribution modelling you can actually defend in a board meeting.

  • Content performance beyond clicks

    Assisted conversions, engagement decay, content decay curves, pipeline attribution for long cycles, and the honest limits of each.

  • Dashboarding and analytics engineering

    Looker Studio, Metabase, BigQuery patterns, dbt models for marketing data, cost-aware warehouse design for small teams.

Editorial bar

What publishable looks like.

  • 1,500–3,500 words typical. Longer if the subject earns it; shorter if you can land the point.
  • Show your work. Screenshots, SQL, code snippets, charts, real data. Anonymise vendor names when using client work, but keep the specifics real.
  • Original to this publication. Not cross-posted, not syndicated, not lifted from a Medium draft.
  • A clear point of view. Opinions grounded in experience. “It depends” is fine only if you explain what it depends on.

What we decline:

PR-driven “thought leadership”, vendor-fawning pieces, reheated listicles, roundups built from other people's quotes, or anything that reads like it was briefed by a link-building team.

What you get

A real partnership, not a placement.

  • A byline and a 200-word bio with links to your personal site or LinkedIn. Your name on the piece, your work attached to your identity.
  • Editor partnership — a senior editor works with you through 2–3 drafts: structure, argument, evidence, headline. You leave with a better piece than you arrived with.
  • Publication on a blog read by working practitioners — SEO operators, RevOps, analytics engineers, and marketing leads at companies who take measurement seriously.
  • Honest distribution in our weekly dispatch. No paid boost, no vanity metrics — if the piece is good, the subscribers decide.
  • Feedback on the angle before you write. We will tell you if the direction is working — or not — in a short conversation, not after you have spent six hours drafting.

How to pitch

The pitch flow.

Whether this is your first time contributing to a publication or your twentieth, the process is the same. Short pitch first, conversation second, draft third.

  1. 01

    Send a 3–5 sentence pitch

    Working angle plus one concrete data point or insight that makes the piece specific. Something only you could write.

  2. 02

    Include proof of work

    Link to something you have written, shipped, or spoken at — a blog post, a talk, a public GitHub repo, a deck. Anything that shows craft.

  3. 03

    We reply within 5 business days

    With acceptance, pushback on the angle, or a polite decline. No ghosting, no "we'll circle back" with no follow-up.

  4. 04

    First-time contributors: please do not send a full draft

    We want to discuss the angle before you invest the hours. One good editorial conversation saves a week of wrong-direction writing.

Use the form to the right to pitch your SEO article or contribute marketing analytics writing. One pitch per message, please — it makes it easier for the editor to respond with something useful.