Ads
Fill Meridian's six ad slots plus the homepage in-feed from Ghost pages — image banners or AdSense code. Off by default; paying members read ad-free unless you decide otherwise.
Meridian has six fixed ad slots, plus a repeatable homepage in-feed. You fill a slot by creating a Ghost page and putting your ad in the page body — the theme finds that page and renders it into the matching spot. One page holds either a static image banner or ad-network code (Google AdSense, Google Ad Manager, or any other network), so the same simple step covers both.
Ads are off by default, hidden from paying members unless you decide otherwise, and a slot you don't fill simply doesn't appear — so turning ads on never leaves blank gaps or breaks your layout. Who sees each ad is yours to choose: see Who sees ads.
The whole system in one sentence
Flip one switch (Enable ads), then create one page per spot you want to fill. No page, no ad in that spot.
Quick start
Turn ads on
Go to Settings → Design & branding → Customize → Theme → Site wide and switch Enable ads on. Save.
Create a page
In Ghost Admin, open Pages → New page. Give it a title for your own reference (it is never shown), for example "Ad — Post footer".
Point it at a slot
In Page settings, set the Page URL to the slot's slug (for example ad-post-footer). That slug is how the theme knows where the ad goes. One slot, the homepage in-feed, uses a tag instead — see below.
Add your ad and publish
Put an image banner or your ad-network code in the page body, then Publish. The ad appears on the next page load.
That is the whole flow. Repeat for each spot you want to fill. The rest of this page is reference: where each slot is, what size to use, and how to handle desktop vs. mobile creatives, AdSense, and privacy law.
Where ads can go
Header leaderboard

A full-width banner at the very top of the site, on every page. Slug ad-header.
Home top

Below the lead stories on the homepage, above Editor's Picks. Slug ad-home-top.
Homepage in-feed

Between homepage sections, and you can place several in any order. Tag #home-ad.
Archive in-feed

Between rows on section, tag and author pages. Slug ad-feed.
In-article (lead)

At the top of a post, above the story, and hidden from readers who can't open the article. Slug ad-in-article.
Post footer

At the end of a post, before the author card. Slug ad-post-footer.
Mobile anchor

A small sticky banner pinned to the bottom on phones, with a close button. Slug ad-mobile-anchor.
Slug vs. tag — the one thing to get right
Six slots are matched by the page's URL slug (ad-header, ad-home-top, ad-feed, ad-in-article, ad-post-footer, ad-mobile-anchor) — one page each, with that exact slug. The homepage in-feed slot is the exception: it is matched by the internal tag #home-ad, so you can create several and order them. Set a slug in Page settings → Page URL; set a tag in Page settings → Tags.
Size reference
One table for every slot. Sizes are pixels (width × height), all standard IAB units. Each slot offers the full width of its largest listed size, so a correctly sized ad renders at true 1:1 and is never scaled down.
| Slot | Create with | Where it appears | Desktop size | Mobile size |
|---|---|---|---|---|
| Header leaderboard | slug ad-header | Strip at the very top, site-wide | 970×90 or 728×90 | 320×100 or 320×50 |
| Home top | slug ad-home-top | Below the hero, above Editor's Picks | 970×250 or 728×90 | 300×250 or 320×100 |
| Homepage in-feed | tag #home-ad | Between homepage sections | 970×250 or 728×90 | 300×250 or 320×100 |
| Archive in-feed | slug ad-feed | Between rows on section / tag / author pages | 970×250 or 728×90 | 300×250 or 320×100 |
| In-article (lead) | slug ad-in-article | Top of a post, above the story | 300×250 or 336×280 | 300×250 |
| Post footer | slug ad-post-footer | End of a post, before the author card | 300×250 or 336×280 | 300×250 |
| Mobile anchor | slug ad-mobile-anchor | Sticky bottom bar, phones only | (hidden) | 320×50 or 320×100 |
Set up a slot
The steps below are the same for every slug-based slot (ad-header, ad-home-top, ad-feed, ad-in-article, ad-post-footer, ad-mobile-anchor). The homepage in-feed slot uses a tag instead — see its note further down.
Create the page
Pages → New page. The title is not displayed — name it for yourself (e.g. "Ad — Header").
Set the slug
In Page settings, set the Page URL to the slot's slug. Don't link it from your navigation.

Add the creative and publish
Put your banner or ad code in the body (next section), then Publish.
The page is the on/off switch for that slot
Set the page to draft or delete it to remove just that slot. Leave the body empty and nothing renders. No template editing, ever.
Choose your creative
A slot's page body holds either kind of ad. Pick a tab.
Slot-specific notes
Most slots follow the steps above. These few behave a little differently.
Who sees ads
Three things decide, and they stack: a site-wide audience, each ad page's own access setting, and a per-story opt-out. All three live in Ghost Admin; no code involved.
Step 1: pick the site-wide audience
Ads audience (in Site wide, shown once Enable ads is on) picks who is served ads across the whole site. Readers outside it get no ad and no ad script.
Go to Settings → Design & branding in Ghost Admin and click Customize.
Expand the Theme → Site wide group on the left.
Open the Ads audience dropdown and pick one of the three options below.
Click Save.

| Ads audience | Visitors (not signed in) | Free members | Paid members |
|---|---|---|---|
| Visitors and free members (the default) | ads | ads | ad-free |
| Visitors only | ads | ad-free | ad-free |
| Everyone | ads | ads | ads |
Complimentary and gift memberships count as paid. Nothing changes when you update the theme: existing sites start on Visitors and free members, which is how Meridian has always behaved.
Step 2 (optional): narrow one ad with its page's access setting
Every ad is a Ghost page, and every Ghost page has an access setting that decides who may read it. Meridian reads that same setting on an ad page to decide who is served that one ad. It is the dropdown labelled Page access in the page settings sidebar (posts carry the same control as Post access), with the same four choices:
- Public: everyone the Ads audience allows (the default; every existing ad page already has it).
- Members only: signed-in members, free or paid.
- Paid-members only: paying members.
- Specific tier(s): members on the tiers you pick.
Go to Pages in Ghost Admin and open the ad page (for example ad-header).
Click the settings icon in the top-right corner of the editor to open the Page settings sidebar.
Under Page access, choose who this ad is for. For Specific tier(s), pick the tiers in the box that appears below.
Click Update (or Publish for a new page).
The access dropdown on an ad page

Specific tier(s)

The two settings stack: a reader must be inside the Ads audience and allowed by the page. A reader the page excludes is never served that slot: no empty box, no divider, no gap. The slug or tag still places the ad; the access setting only decides who it is served to.
| You want | Ads audience | Ad page access |
|---|---|---|
| Ads for visitors and free members; paying members read ad-free (the default) | Visitors and free members | Public |
| Ads for everyone | Everyone | Public |
| Ads for logged-out readers only, so a free account is the ad-free upgrade | Visitors only | Public |
| An "upgrade to go ad-free" house ad, shown to free members only | Visitors and free members | Members only |
| A sponsor message for members only | Everyone | Members only |
| A thank-you offer for one tier | Everyone | Specific tier(s) |
Change access on an ad page at any time
Access on an ad page works like access on any page: Ghost simply doesn't deliver the body to readers it excludes, and the theme renders nothing in that slot for them. Your other ads and your layout are untouched. Nothing to re-publish, no code to touch.
Step 3 (optional): keep ads off one story
Add the internal tag #no-ads to a post or page and it is published without any ad: no slots, no ad script. Use it for sensitive stories, sponsored content, or anything an advertiser should not sit beside. The walkthrough, with screenshots, is in Editorial conventions → No ads.
Where ads never show
- The membership page (the page slugged
join) carries no ads and loads no ad script, whatever the settings, so nothing competes with checkout. - A story tagged
#no-ads, as above.
Sell the ad-free read
Readers notice when an upgrade removes ads, so say so: add Ad-free reading to your paid tier's benefits in Settings → Membership → Tiers. The theme never claims it for you, so the benefit appears only where you put it.
Google AdSense
Add your publisher ID
In Site wide, set AdSense publisher ID to your ca-pub-XXXXXXXXXXXXXXXX. Meridian then loads the AdSense script once, so you can use Auto ads and manual units.

Place manual units
Paste each ad unit's code into the slot pages above.
Prefer to manage the loader yourself? Leave the publisher ID blank and add your script via Settings → Code injection — Meridian respects whatever you put there.
Auto ads anchor vs. the theme's mobile anchor
AdSense Auto ads can place its own anchor/overlay ad at the bottom of the screen. If you also fill the theme's mobile anchor slot, phones get two stacked sticky bars. Use one or the other: either skip the ad-mobile-anchor page, or turn off the Anchor format in your AdSense Auto ads settings.
ads.txt
For programmatic / AdSense verification you will likely need an ads.txt file at your domain root (e.g. https://yoursite.com/ads.txt). This lives at the server / Ghost level, not in the theme: on Ghost(Pro) and most hosts you add it through your platform; self-hosters can place ads.txt in the theme's root folder and re-upload. It is publisher-specific, so Meridian doesn't ship one.
Privacy & compliance
You (the site owner) are the data controller. Meridian provides consent-ready plumbing; you choose and configure a consent solution. This is configuration guidance, not legal advice.
Static image banners are exempt
A plain image banner sets no cookies and does no tracking, so it needs no consent and triggers no banner. The notes below apply only to ad-network code.
Mobile & layout
Every slot is responsive: fluid, centered, capped to its surrounding content width, with reserved height so the page doesn't jump as an ad loads. Oversized creatives are clamped so they never cause sideways scrolling. The mobile anchor pads the page bottom so it never hides your footer. Ads are labelled "Advertisement" (translated automatically on non-English sites).
For readers who aren't served an ad (see Who sees ads) and when ads are off, no slot markup renders at all — your layout is byte-for-byte what it is today, with no empty boxes or stray dividers.
Turning ads off
- One slot: unpublish or delete that slot's page.
- One slot, for some readers: change that page's access setting. See Who sees ads.
- One story: tag it
#no-ads. - For members: set Ads audience in Site wide to Visitors and free members (the default) or Visitors only.
- Everything: switch Enable ads off in Site wide. All slots stop rendering and no ad scripts load.
Glossary
Signup forms
Meridian's signup forms follow your Ghost signup settings, just like Ghost's own signup popup. They show your signup notice, can require agreement before anyone joins, and ask for a name when Ghost does.
Publication Language
Meridian ships in 14 languages. Set your publication language in Ghost Admin and the theme's interface adapts automatically — no code or manual translation needed.

