SEOMANTIK
Choose a plan
01seomantik-topic02seomantik-content03seomantik-outreach04seomantik-ads
04The advertiserComing soon

Your plan in. Paused campaigns on your own ad account out.

seomantik-ads turns the commercial side of your plan into Search campaigns, checks every landing page before a term is attached to it, and builds on your account on your go. Every campaign is born paused. Once it serves, it reads what clicks really cost from your account and feeds the search terms back into the plan.

Runs on your own ad account and credentialsEvery campaign is born paused
NeedsYour Google Ads account connected. A topic run gives the campaigns their skeleton; without one, you name what you sell, the terms you want and the page for each.
See the 5 steps
claude ~/seomantik/yourdomain.com
Run seomantik-ads on yourdomain.com
·Market en, US, from the plan. Account chosen: live, currency USD
·Spend plan: 2 clusters, on your daily budget and your click ceiling. No forecast
·Destinations: 4 pages ready as landing pages, 1 to fix first, 1 wrong page, reasons in the file
Wrote data/ads/spend-plan.json
Wrote data/ads/destinations.json
Ready to build. Say go and the campaign is created paused on your account.
What it does, in order

Five steps, from your plan to campaigns in your account.

0Setup

What the account is (a test account is a sandbox, and the skill says so every time), what is already in it, which market, which currency, your daily budget range and the most you will pay for one click. It reads the plan's artifacts when they exist and asks for the niche, country and language when they do not; the currency comes from the ad account you pick. It never assumes any of them.

→ Account · market · currency · your ceilings
1The spend plan

Which clusters of your plan get money, how much a day, and the most any one click may cost: both numbers yours. The plan ranks clusters by intent and by whether their landing page exists. There is no forecast and no guess at the market. Exclusions keep you from paying for the questions your articles already answer.

→ Your numbers, no forecast
2Destinations

Which pages deserve ads and which do not, read as landing pages: where the terms appear, whether the page keeps the ad's promise, whether a visitor can act. Before a single term is attached to them.

→ 4 ready · 1 fix first · 1 wrong page
3Build

The campaigns, ad groups, keywords, negatives and ads, created in your account on your go, and born paused. Starting one is a separate decision you make.

→ Created paused
4Operate

Once a campaign serves, your account shows what nobody could know before: what a click really costs, how often the ads showed, how much showing was lost to budget and how much to rank, and Google's quality score for each keyword. The search terms go back into the content plan.

→ Your account's numbers → next wave
Setup · nothing assumedSpends nothing
claude ~/seomantik/yourdomain.com
Run seomantik-ads on yourdomain.com
·Reading the plan in this folder. Niche sourdough, market United States, language English.
·Plan artifacts found: architecture, questions, build list.
·Two ad accounts reachable. Which one should the plan use?
The yourdomain.com account
·Account currency USD, time zone New York. Every money line from here is in USD.
·A working daily budget range in USD, the most you will pay for one click, and anything off-limits: brands not to bid on, regions to avoid?
A small daily range to start, a click ceiling I can live with. No other companies' brand names, and nothing outside the US.
·Budget range, click ceiling and off-limits noted. The ceiling is yours, not a prediction of what clicks will cost.
Setup done. Nothing created, nothing spent.
A test account is called a sandbox, every time: real campaign objects, zero serving, zero spend.
The spend plan · you pick, the plan ranksdata/ads/spend-plan.json
Cluster, and its caseDaily budget · click ceiling, USD
HydrationIn the planNames what the page sells, page liveyour figure · your figure
TroubleshootingIn the planA problem the page solves, page liveyour figure · your figure
StartersLaterIts page is still on the build listnone yet
BakingNot fundedInformational: its terms become negativesnone
No forecast, no bidder count, no cost estimate. The only number beside a budget is arithmetic: the budget divided by the ceiling is the fewest clicks a day if every click cost the full ceiling. The plan also sets the date your account is first read. Which clusters get money is your decision; the ranking is advice.
Ad money is yours, in your own account, and never moves without the go.What clicks really cost is read from your account once it serves.
Destinations · checked as landing pages4 ready · 1 fix first · 1 wrong page
PageRelevance to the termsTermsWhat the page saysSaysA way to actGoogleVerdict
/guides/hydrationReady
/guides/starter-readyReady
/recipes/beginner-loafReady
/equipment/dutch-ovensReady
/aboutNot this pageNo
No content on the term: a general page about the site, so an ad for hydration would land a stranger nowhere.
/blog/2019-updateFix firstFix
A 2019 update post: the terms are not in its title or headings, and the ad's promise is nowhere on it. Fix it first, or wait for the page.
Each verdict comes with the evidence behind it, never a bare score. A page that fails gets its fixes named.A page that does not exist yet gets a brief, written from your plan's own questions for that cluster; you defer the campaign or point it at the best existing page, with the mismatch named.Before the build it checks that the account can see a sale: a primary, enabled conversion of the right kind, with its goal set to steer bidding. If either is missing, it proposes the fix, gated, and hands over the exact tag.Page speed is not measured here. Google's own verdict on each landing page is read from your account once the campaign serves.
Build · on your explicit goBorn paused
CampaignSearch, hydration clusterDaily budget: the plan's figure, in USD
Ad groupBeginner loaf hydration→ /guides/hydration
KeywordsPhrase and exact, from the plan's keywords for the clusterNever broad
NegativesThe questions your articles already answere.g. "how to feed a starter"
AdOne responsive search ad, written from the page's own headingsPromises what the page delivers
Ad groupHigh hydration technique→ /guides/high-hydration
PAUSED
·Would create, paused: one campaign, two ad groups, their keywords, negatives and one ad each, at the plan's daily budget in USD. Target United States (country). Each click capped at your ceiling. One operation: all of it lands or none of it does. Nothing exists yet.
·Say go to create it. Starting it is a separate go, previewed the same way, whenever you are ready.
The preview names the resolved place, so you approve a place, not a string.
Operate · what your account measuredPaid data feeds the next wave
What people actually typedClicksIn the plan?
"sourdough too sour fix"41New question
"starter smells like acetone"28New question
"best flour for starter"63Already planned
"how to feed a starter"19Add as negative
Campaign servesStarted by you, on a previewed go
Account readCost per click, share of searches shown, quality score. First read on the date in the plan
Next waveNew questions go into the plan
Example rows. New questions become pages; terms your articles already answer become negatives, which only lower spend. It reads your own numbers only: which other advertisers appear on the same searches is not available to it.
What lands on your disk

Files in your project folder, paused campaigns in your own account. Both, always.

The ads connection is required. It runs on your machine, in your account, with your credentials, through no account but yours.

data/ads/spend-plan.jsonyour numbers, no forecast
Spend plan
hydrationyour budget · your ceiling
troubleshootingyour budget · your ceiling
starterslater, page on the build list
ad money yours, $0 spent
data/ads/spend-plan.json · data/ads/destinations.jsonTwo files: the spend plan, and the destinationsspend-plan.json is the clusters, the daily budget and click ceiling for each, keywords and exclusions, no forecast. destinations.json is which pages deserve ads and which do not, with the reason for each, plus the conversion-tracking handover.
data/ads/account-read.jsonwritten once the campaign has served
The account read
cost per clickfrom your account
share of searches shownlost to budget · lost to rank
quality scoreper keyword
dated, traced to the saved report
data/ads/account-read.jsonThe account readWhat clicks cost, how often the ads showed, what held them back, and quality score per keyword. Dated, and traced to the saved report.
your ads accountcampaigns.json keeps the ids
Search · hydration cluster ● pausedad group · beginner loaf hydration12 keywords · 8 negatives1 ad → /guides/hydrationspend to date: $0
campaigns, pausedThe build, in your accountCampaigns, ad groups, keywords, negatives and ads, created on your go and born paused. Starting one is its own previewed go.
Rules it always keeps

What it always does. What it never does.

Reads what clicks really cost from your account, once it serves.
Says when an account is a sandbox, every time.
Checks every destination as a landing page before attaching a term.
Feeds what people actually typed back into the content plan.
Never spends ad money on its own.
Never starts a campaign on its own. Every one is born paused; starting it is its own previewed go.
Never assumes the niche, country, language or currency.
Never forecasts, and never promises performance.
Pricing · a separate productComing soon

Own product, priced when it opens.

Sold apart from the skills subscription. Needs no data account: it reads your plan and your own ad account.

Next in the folder

Next month, run seomantik-topic again: it measures what moved and re-orders the rest.

Back to seomantik-topic →