“Nobody visits your website first. They meet your front door.”
Search the trade plus the town and look at what comes up before anything with your URL on it: the business profile. The hours, the photos, the stars, the questions, the call button. That’s the first impression, and for most customers it’s the only one — they never walk past the door into the house.
Your website is the house. The profile is the front door. Nobody’s impressed by the house if the door is boarded up.
The door inventory
Walk up to your own front door like a stranger and read what’s on it:
The hours — including the holiday hours, the ones that are wrong on half the profiles in America right now. The photos — the truck, the crew, the work, or a gray empty storefront from 2019. The reviews — stars, words, and whether anyone from the business ever answered back. The questions — asked by strangers, answered by strangers, when nobody from the business is home. The posts — the weekly update slot, empty since the profile was claimed. And the two big brass buttons: call, and directions.
That’s the door. Every customer reads it before they knock.
The untended door
Here’s what most front doors look like: hours that lie on holidays. Photos older than the crew in them. A Q&A section where a stranger asked “do you do water damage?” eight months ago and another stranger answered “idk.” No posts — the business has done a hundred jobs since the profile went up and the door shows none of them. Reviews sitting unanswered, the digital equivalent of mail piling up in the slot.
And the doorbell — the call button — still works. It rings. Right into the voice line, right into the tuition piece. The door and the phone are the same system: the profile is where they decide to knock, the line is what answers.
An untended door doesn’t just lose the knock. It sends the customer to the next door on the street — the competitor whose hours are right and whose photos are from this year.
Tending the door
The good news: tending a front door is a fifteen-minute weekly ritual, not a project.
Fresh photos — the actual truck, the actual crew, the actual work from this month. A door with fresh photos says “we’re alive in here.” Check the hours — especially before holidays, the highest-traffic lying season. Work the Q&A — seed the questions customers actually ask, answer them in your own voice, so strangers don’t do it for you. One post a week — the job you finished, the storm you worked, the crew milestone. It’s the shop window; put something in it. Answer the reviews — every one, but especially the good ones, because the response is the business talking back through the door.
Fifteen minutes. The highest-traffic page in the business, tended.
The compound
Here’s what makes the door different from every other marketing chore: it compounds and it doesn’t decay.
A post you write stays up. A question you answer stays answered — every future stranger with the same question reads your answer instead of a stranger’s guess. A photo you add joins the set. Reviews you respond to stack into a record of a business that talks back. Nothing you do to the door un-does itself. It’s all permanent, all cumulative, all working while you sleep.
Most marketing is rent — stop paying, it stops working. The front door is owned. Every fifteen minutes you spend on it is still there next year.
The close
Your website is the house. Beautiful, expensive, and visited second — if ever.
The profile is the front door. It’s what they see from the street, it’s where they decide, and the doorbell on it rings straight into your line. Tend the door. Sweep the step. Put something alive in the window. Answer when they knock.
Nobody ever hired the house. They hired the door that looked like somebody was home.
For twenty years, SEO was link-building. Other sites vouching for you, one hyperlink at a time. That game is over — and the replacement is sitting in your Google Business Profile, mostly ignored.
Your reviews are your new backlinks.
Why trust moved
An answer engine recommending a contractor at 2 AM is making a trust decision. It can’t inspect your trucks or interview your techs. It reads signals — and the richest trust signal a local business produces is the public record of its customers, in their own words.
Links said “this site is authoritative.” Reviews say “this company showed up, did the work, and a real human vouches for it.” In the answer era, the second statement is worth more than the first.
The three layers
Not all reviews are fuel. Three layers separate the profiles that get cited from the ones that don’t:
1. Volume and recency. A profile with 200 reviews and nothing in three months reads abandoned. The engine notices recency the way a homeowner notices dust. Trust is a flow, not a stock — it needs refilling.
2. Content. “Great service, highly recommend” is noise. It says nothing the engine can verify. Compare: “They dried out our kitchen after the dishwasher supply line burst, here in Puyallup, and had fans running the same day.” That’s a service, a place, a timeline, an outcome — verifiable detail from a third party. That’s citation fuel.
Most contractors get the first kind because they ask for “a review.” The second kind comes from asking a better question — more on that below.
3. Responses. The owner answering every review — good and bad — is the consistency discipline made visible. It proves there’s a human tending the business. The engine reads a thoughtful response as operational evidence: this company pays attention.
How to ask
Don’t ask for “a review.” Ask at the moment of relief — the equipment’s out, the house is dry, the stress is gone — and make it specific:
Send the direct link. Every extra tap loses half your ask rate.
Prompt for the details: what happened, where, how fast. “Mention what we fixed and how quickly” is a fair ask, and it turns noise into fuel.
Ask the happy ones. The tech knows who they are. Build the ask into the job-close routine, not into a quarterly campaign.
One detailed review a week beats fifty generic ones a year.
The bad review is content too
Answer it like the answer engine is reading — because it is. A calm, specific, human response to a one-star review is some of the strongest trust content a profile can carry. It shows how the company behaves when things go wrong, which is exactly what a 2 AM homeowner is trying to figure out.
Never argue. Never go silent. Own what’s ownable, state what happened in plain words, invite the conversation offline. The response isn’t for the reviewer — it’s for the hundred strangers reading it after.
What reviews don’t replace
The pages still matter. The GBP still matters. Name, address, phone — consistent everywhere — still matters. Reviews are the fuel, not the engine. A hundred five-star reviews on a profile with the wrong phone number is a fast car with no wheels.
But given the foundation, reviews are the highest-leverage work in local trust. Nothing else you do produces third-party verifiable detail at zero marginal cost.
The close
Backlinks were other websites vouching for you. Reviews are your customers vouching for you, in public, in their own words, attached to real jobs in real towns.
The currency changed. The game didn’t. Get vouched for.
Last week I argued the agency retainer has to re-anchor to cited pages — not pages published, but pages the answer engines actually cite. That was the claim. This is the how.
Because a metric you can’t operate is a slogan. And slogans don’t survive the Monday-morning meeting.
The lie in the dashboard
Open any agency report and you’ll see the same furniture: pages published, posts written, keywords ranked, traffic graphed. It all measures manufacturing output. It answers “what did we make?” — a question nobody is asking anymore, because the making is free now.
Here’s the question your client is actually asking, usually without saying it: when my customer asks their AI who to call, does my name come out of its mouth?
Everything else is decoration.
Churn vs. growth: the identity test
Five pages cited today plus five different pages cited tomorrow is not ten citations. It’s churn.
A page cited in March and still cited in September is an asset — it means an answer engine trusts that page enough to keep serving it. A page cited once, in one answer, on one Tuesday, is a lottery ticket. It might mean something. It probably means nothing.
This is the identity test: don’t count citations. Track which pages get cited, over time. Growth is the same pages showing up month after month, plus new ones joining them. Churn is a revolving door of one-hit wonders. Most “AI visibility” dashboards report the revolving door and call it growth. Now you know the difference.
The ledger
You don’t need software for this. You need a ledger — one row per page that matters:
The page — its URL. Identity is everything.
The question — the money question it answers. Not vanity queries; the ones a customer asks right before hiring. “Who do I call for a flooded kitchen in Tacoma” beats “water damage restoration tips” every time.
The engine — which AI cited it. They don’t all agree, and the disagreement is information.
First cited — the date it showed up.
Still cited — checked weekly. Yes or no.
That’s it. Five columns. This is the bait board: every page is bait on a hook, and the ledger tells you which hooks are catching fish and which are just sitting in the water.
Run it weekly. Ask the engines the money questions directly — the way your customer would ask, in their words, not keyword-ese — and write down whose pages come back. It takes an hour. The hour is the product.
What earns the citation
After a few weeks the ledger starts talking. The pages that persist share a shape:
One clear answer. Not a comprehensive guide — an answer. The engine is trying to complete a sentence for the user, and it cites the page that completes it best.
Real proof. Job photos, real addresses, real outcomes. Anything the engine can cross-check against the rest of the web. Fabricated authority rots; verifiable detail compounds.
A consistent identity. Same business name, same service area, same story everywhere the engine looks. Trust is a pattern, and patterns need repetition.
Notice what’s not on the list: word count, publishing frequency, “optimization.” The manufacturing variables don’t move the needle. The trust variables do.
The report worth paying for
Now rewrite the monthly report. One page:
Which money questions your client shows up inside, and in which engines.
Which pages earned those citations, and how long each has held.
What’s new, what’s gone quiet, and what you’re doing about the quiet ones.
One judgment call: the question you’re going to win next, and why.
No page counts. No “optimizations completed.” Just presence, persistence, and a plan. That’s the report a contractor can’t generate from their own AI stack — because their stack can mint pages, but it can’t tell them which questions are worth winning or notice when an engine changes the rules.
The judgment layer
And that’s the actual product. The ledger is bookkeeping; the judgment is the business:
Which questions are worth winning. Money questions, not vanity ones. Ten citations for questions nobody asks before hiring are worth less than one citation for the question they ask with water on the floor.
What proof to build next. The ledger shows you which pages are one citation away from sticking — that’s where the next job photo, the next real answer, goes.
When to change course. An engine updates, a persistent page drops off, a competitor’s page takes its place. Somebody has to notice in week one, not quarter three.
AI can do the bookkeeping. It can’t do the noticing. It can’t decide what matters. That’s the human gate, and it’s the whole retainer.
The close
The agency bringing page counts to the Monday meeting is bringing manufacturing output to a client whose own AI manufactures for free. That meeting gets shorter every month.
The agency bringing the ledger — which questions, which pages, how long they’ve held, and what wins next — is bringing something the client’s stack can’t make: judgment, tracked over time, with receipts.
Stop counting pages. Count citations. Then make the citations compound.
It’s the question every agency dreads. It shouldn’t be. It’s the best question a client can ask — because the honest answer is the whole business.
Here’s the honest answer: you’re not buying pages.
Pages are free now
An AI can produce a thousand service pages before lunch. Decent ones, even — clean structure, correct grammar, plausible advice. Page production, the thing agencies sold by the unit for twenty years, now costs approximately nothing.
So if your agency’s $995 buys you pages, you’re buying manufacturing in the age of the factory. That’s not a retainer. That’s a nostalgia subscription.
The agencies that survive already know this. The ones that don’t are still sending you a monthly report that says “we published 8 pages” like it’s 2019.
What the money actually buys
Strip out the manufacturing and what’s left is the part that was always the real product — it was just hiding inside the page count. The $995 buys five things:
1. The judgment of which questions to win. Anybody can publish fifty pages. Somebody has to decide which ten questions are yours — the ones your best customers ask right before they hire you, in the towns you actually serve. That’s a decision, not a deliverable. It requires knowing your business, your market, and your proof. AI can’t make it for you; it doesn’t know which jobs you want more of.
2. The proof operation. Cited pages win on verifiable detail — real job photos, real street names, real outcomes. Somebody has to collect that proof: get the photos off the techs’ phones, attach them to the right jobs, write down what happened in plain words. Nobody enjoys this work. That’s why it’s valuable.
3. The citation watch. Every month, somebody checks: which of your pages is the answer actually citing? Which ones held their position, which ones slipped, which questions got taken by a competitor? This is the ledger. Without it you’re publishing into the dark.
4. The consistency discipline. Same business name, same service area, same number — everywhere. Reviews answered, photos current, hours correct. Boring, relentless, and directly downstream of whether the answer trusts you at 2 AM.
5. A monthly report that means something. Not traffic. Not rankings. Cited questions, cited pages, persistence, losses, and the next question to win. One page, five numbers, and a decision about where the next month’s effort goes.
That’s the retainer. Not manufacturing — maintenance of a position.
What it doesn’t buy
It doesn’t buy vanity traffic reports. It doesn’t buy a blog schedule. It doesn’t buy a redesign every eighteen months. It doesn’t buy keyword rankings, which measured a game that ended.
If your agency’s monthly report leads with how much they made instead of what position you hold, you’re paying for the factory.
The reframe
Think of it like a lobbyist, not a factory. You don’t pay a lobbyist per meeting or per phone call — you pay for a maintained position. Access held, relationships warm, your name in the room when the decision gets made.
The $995 holds your position in the answer. The answer changes daily — competitors publish, engines update, questions shift. A position unattended decays. Somebody tends it, or nobody does.
The pages are just the visible part, the way a lobbyist’s suit is the visible part. Nobody’s paying for the suit.
The close
Ask any agency the $995 question. “What exactly am I paying for?”
If the answer is deliverables — pages, posts, reports — walk. Deliverables are free now.
If the answer is a position — which questions you’re winning, how long you’ve held them, what’s next — stay. That’s the thing that can’t be manufactured.
A vendor just published the obituary for my industry. “90% of SEO agencies will be irrelevant by 2026.” It’s a sales pitch dressed as a prophecy — they’re selling their own “hyper-intelligent SEO,” so of course the old model has to die first.
Here’s the uncomfortable part: they’re half right.
The steelman
Their argument, at full strength: AI has already absorbed keyword research, content outlines, and technical audits. The page-minting labor — the thing agencies billed hours for — is now a commodity any contractor can run from their own AI stack. And niching down doesn’t save you, because AI flattens execution across every niche equally. A restoration-only agency mints pages the same way a dental-only agency does: same models, same prompts, same output.
Then the sharpest line, aimed straight at a $995/month retainer like ours: monthly payments masked declining perceived value while clients stayed only because switching felt risky. Inertia as a business model. And inertia collapses the moment the contractor’s own AI handles the page work in-house.
Read that twice. It’s the most dangerous true thing anyone’s said about my business this year.
Where they’re wrong
Execution was never the product. It was the packaging.
Nobody ever paid an agency for pages. They paid for the judgment about which pages, in which order, aimed at which questions — and for someone to notice when the game changed and change with it. The page was the receipt, not the purchase.
What actually died is the retainer that sold counts: X city pages, Y blog posts, Z “optimizations” per month. Count-based selling trained clients to audit deliverables instead of outcomes, and it trained agencies to manufacture deliverables instead of outcomes. AI didn’t kill that model. It just made the manufacturing free — which exposed that the model was already hollow.
What survives is the part AI can’t commoditize: being present inside the answer. When a homeowner asks their AI assistant who to call for a flooded kitchen, somebody’s name comes out of its mouth. That presence isn’t won by page counts. It’s won by being the source the answer engines trust and cite — clear answers, real proof, a consistent identity across the web. That’s judgment work. It has a human gate. It doesn’t scale into a commodity, because trust doesn’t scale into a commodity.
The re-anchor
So we’re re-anchoring the sprint to the only number that matters: cited pages. Not pages published — pages the answer engines actually cite, tracked by identity over time. Five cited today plus five different tomorrow is churn, not growth. The metric is persistence: which of our pages keep showing up inside answers, month after month.
The $995 doesn’t buy GBP tweaks and city-page counts anymore. It buys a standing position inside the answers your customers are already asking for — and the judgment to keep it there as the engines change the rules. That’s a strategy partner, not a page vendor.
What changes Monday
If you run an agency, or you buy from one, here’s the Monday-morning version:
Kill count-based reporting. If your monthly report leads with pages published, posts written, or “optimizations completed,” you’re reporting manufacturing output. Nobody buys that anymore — they can manufacture it themselves.
Report cited presence instead. Which questions do your clients show up inside? Which pages got cited, by which engines, and are the same pages still cited next month? That’s the report worth paying for.
Price the judgment, not the labor. The labor is free now. What’s scarce is knowing which questions are worth winning, what proof earns a citation, and when to change course. Put that on the invoice or someone else will.
The 10%
The vendor’s prophecy ends with 90% irrelevant. Fine. Let them have the 90% — they were selling page counts, and page counts are free now.
The 10% that survive won’t be the ones with the best AI stack. Every agency will have the same models. They’ll be the ones who stopped selling execution before the market forced them to — and started selling the one thing the models can’t mint: being the answer.
I built a small tool called PageReady. It scores a web page for two kinds of readiness, and today I’m putting it on GitHub for anyone to use however they want. MIT license. As-is. No support desk.
Most page audits give you a score out of 100 and a list of suggestions you’ll never get to. PageReady is binary: PASS or FAIL, on two axes.
1. Citation readiness (AEO). Can an AI answer engine cite this page? It checks for one H1, a sane heading hierarchy, JSON-LD structured data, a table signal, and FAQ-style questions — the things that make a page quotable.
2. Agent interaction readiness (DOM). Can an AI agent actually use this page? It checks for a main landmark, named controls, semantic interactive elements, heading order, and form labels — the things that make a page operable.
Overall PASS requires both. And here’s the insight that made the tool worth building: fixing your headings can lift the shared heading gate, but it does nothing for clickable div cards. A page can be perfectly citable and completely unusable by an agent. Most audits conflate the two. They’re different problems.
How you use it
It’s a local command-line tool, a stdio MCP server, and an optional HTTP API you can host yourself (there are Cloud Run deploy scripts). No API keys required — it scores pages directly, nothing phones home.
As an MCP server it exposes three tools:
score_page — score one public URL, returns a JSON scorecard
score_site — score a batch of URLs, with pass/fail counts
explain_gates — describe every check and the overall PASS rule
Point your agent at it and ask whether a page is ready. Exit code 0 means PASS. Exit code 1 means FAIL. That’s the whole interface.
Why open source, why as-is
The scoring logic was never going to be the moat. It’s a commodity check — the value is in knowing which pages to run it on and what to do with the answer. That’s the work I do with clients every week, and no repo replaces it.
So the repo is bait, not the business. If it saves another developer an afternoon, good. If someone forks it and makes it better, better. If a competitor forks it closed and sells it — the MIT license allows that, and I’m fine with it. The relationships are the hook; the tool is just proof I do the work.
As-is means as-is. No SLA, no roadmap, no support promise. Issues are read on a best-effort basis. I’d rather ship something useful with no promises than maintain something mediocre with a changelog.
The receipts
Before publishing, the repo went through a pre-publish scrub (secrets sweep, license, README rewrite), then three independent model reviews: a security audit (SAFE), a correctness pass (no bugs), and a docs review (pass). The scrub caught one hardcoded cloud project ID, which is now an environment variable (GCP_PROJECT). That’s the whole incident report.
AI citations don’t come from pages alone. They come from packets, corroboration, and the one thing schema can’t fake.
William Tygart · Tygart Media
The morning I thought we’d been delisted
I thought we’d been delisted.
Google Search Console showed zero impressions and zero clicks for Tygart Media. A flatline. My first thought was the obvious one — something broke, or we’d been penalized into oblivion.
We hadn’t. Bing showed real traffic the whole time. Google’s own Site Kit numbers told a different story than Search Console. The site was fine. The dashboard was measuring the old world.
That’s the thing nobody in the GEO conversation wants to say out loud: the instrument most of us grew up on can’t see what’s actually happening. AI citations don’t show up in Search Console. The traffic is real; the attribution is invisible. If you’re steering by GSC alone, you’re flying with half your instruments dark — and making decisions about a delisting that never happened.
The packet theory
Here’s what I keep coming back to: classic search already has the answers. Every question worth asking has been answered somewhere, usually well. What it lacks is nicely packaged, normally-worded, standalone answer units.
So package it up, and they lift it.
An AI answer doesn’t want your page. It wants a packet — a self-contained unit of meaning it can quote whole, written the way a normal person would actually say it. Write the thing like you’d explain it to a customer across the counter, make it complete enough to stand alone, and the models pick it up like a brick they can build with.
“The page is not the product. The packet is.”
This is where most GEO practice misses. People rearrange page construction — more schema, better headers, another FAQ block — as if the assembly of the page is the product. It isn’t. GEO is more than how pages are constructed. The pages are just where the work becomes visible.
Off-page weights
I was replying to Ira Bodnar about this recently. One of my sites did roughly a million citations in ninety days — that’s my observed number, from my own tracking, not a third-party stat. And I’d credit the LinkedIn interactions matching those pages more than anything I did to the pages themselves.
Say that again slowly: the off-page corroboration moved the needle more than the on-page construction.
Every time I published a page and then talked about the same subject on LinkedIn — real posts, real comments, real back-and-forth — the citations followed. The models aren’t just reading your HTML. They’re weighing whether the world around the page agrees with it. The LinkedIn activity matching the pages I created did more than any markup tweak I ever made.
“Off-page weights move AI citations. Full stop.”
Different humans altogether
Here’s another one: Claude desktop users and ChatGPT mobile users behave like different humans altogether.
We keep talking about “GPT” or “Claude” like each one is a single portal. It isn’t. Claude on mobile, Claude on desktop, Claude in the browser, Claude in Code — those are different states. The model knows the person and the surface. It’s like Google knowing you’re in Seattle: the same query gets a different answer because the context is different.
There is no one portal called GPT. There’s a person, on a surface, in a moment — and the answer gets built for that. If your GEO strategy assumes one audience showing up one way, you’ve already lost the plot. Segment by surface or don’t bother.
What the server logs show
Nobody in the GEO conversation looks at raw server logs. That’s the edge, and it’s sitting right there.
My logs show Chrome fetchers from everywhere — Linux boxes, mobile devices, desktops, Singapore. Manus, Perplexity, You.com, OpenAI, Grok. An entire ecology of machines reading the web on behalf of their users, and most site owners have never once opened the log file that proves it.
Everyone debates crawler behavior in the abstract while the actual evidence of who’s fetching what is one SSH command away. Look at your logs. The bots will tell you exactly what they care about, if you bother to ask. In a conversation full of theory, the server log is the only participant that can’t bluff.
You still have to connect to the person
Here’s the close, and it’s the whole game: you still have to connect to the person.
Schema doesn’t make anyone feel heard. Markup doesn’t make anyone feel heard. A million citations don’t make anyone feel heard.
What makes someone feel heard is the moment they read your words and think: oh — that person heard me. That feeling is the product. Everything else is packaging.
“That feeling is the product. Everything else is packaging.”
And here’s my dare, the one I mean: go ahead and try to copy what I do. Seriously. Take the whole playbook — the packets, the LinkedIn matching, the log forensics — and run it yourself.
You won’t be able to. Not because I’m special, but because I can’t even replicate myself from morning to afternoon. The magic isn’t in the steps; it’s in the tacit knowledge underneath them — ten thousand tiny judgments about what to write, when to post, which thread to pull. You can’t replicate magic.
Tacit knowledge is the moat.
GEO is more than throwing pages together. It always was.
Open field playbook. No patent. Copy it. Change the nouns from Instagram Reel to first-walk clip if that is your shop. If it stops you from treating a faster poll as a strategy, good.
License: do what you want. Attribution nice, not required. Tygart Media is not a OneUp partner, reseller, or affiliate. Links below go to official product doors. No tracking parameters. No referral codes. No reprint of the vendor email body.
Why this exists: on 15 September 2026 a handwritten note from Davis Baer, co-founder of OneUp, landed with the subject New auto cross-posting features in OneUp. Three product facts. The source check moved from every two hours to every one hour. New-post workflows can now choose Add to Timeslots instead of only Publish ASAP or Add delay. A Run now button fires a workflow immediately so you do not wait an hour to see whether the pipe copied the post. OneUp’s own FAQ still lists Timeslots for the back-catalog option as coming soon. That is the vendor record. The operator problem is the slot, not the clock.
Direct answer
OneUp auto cross-posting watches a Source account on Instagram, Facebook, or TikTok and copies qualifying posts to Destination accounts the product supports. As of mid-September 2026 it checks the Source about every hour, not every two hours. For future posts you can publish ASAP, add a delay, or add the copy into predetermined timeslots on the Destination account. Run now tests the workflow without waiting for the next poll. Image workflows and video workflows stay separate. Keyword include/skip filters from August 2026 still apply. Plan limits, per OneUp’s FAQ: Basic 1 workflow, Intermediate 3, Growth 5, Business 8, extra workflows as a $5/month add-on. Official APIs only. Timeslots on “Cross-post existing posts” is not claimed live here. The Destination clock is still not a local service page.
FAQ that names the poll, sources, and workflow counts: Cross-posting FAQ
Timeslots help (includes the cross-posting “Add to Timeslots” line): Timeslots help
If you do not run the tool, do not scrape the email for a screenshot library. This page does not republish Davis’s pitch or the trial offer.
1. What actually changed
Piece
Before this note
Vendor claim now
Source poll
About every two hours (the number this desk already published on 3 September 2026).
About every one hour.
When the copy publishes
Publish ASAP or Add delay.
Those two, plus Add to Timeslots on new-post workflows.
Prove the pipe
Wait for the next poll.
Run now fires the workflow immediately.
Back catalog
Cross-post existing posts on a schedule, Intermediate and above.
Same option. Timeslots on that option: coming soon, per the vendor note.
A one-hour poll is hygiene. It cuts the lag between a Source post and a Destination copy. It does not decide whether 11:07 p.m. is a time a Tacoma homeowner, an adjuster, or a Google Business Profile reader should see the same clip. ASAP with a shorter fuse is still a reprint machine. The slot is the gate.
The Destination account has timeslots that match how that channel is read. LinkedIn at lunch. Neighborhood Facebook in the evening. Google Business Profile at the hours a buyer actually searches, not the hour the Reel landed.
The Destination post is a pointer. The record lives on your domain and on the Business Profile.
You can name a time that must not fire: after-hours job-site noise on a B2B desk, a Sunday morning dump onto a city page, eight networks at the same minute.
Do not treat Run now as:
Permission to publish. It is a test of the pipe.
A substitute for reading the Destination after the copy lands.
Proof you have distribution. Proof is a cited answer or a booked job.
3. SEO, AEO, GEO — the clock is not the cite
SEO is crawlable pages with one job each. A Destination post scheduled for 1:30 p.m. is still a feed object. It expires. The service page does not. Cross-posting moves the clip. It does not invent the page.
AEO is answer-engine optimization. Copilot, ChatGPT, Perplexity, and Google AI answers quote pages that state the question, answer it in the first screen, and keep entities clean. Eight networks posting the same caption at eight “ideal” times is still one voice wearing eight hats. Timing does not create a cite.
GEO here still means two things at once:
Generative engine optimization — structured enough that models can reuse you without inventing your city.
Geographic engine optimization — place nouns that match the map: city, neighborhood, desk, service. And, on this drop, when a place-bound channel is allowed to speak.
A timeslot is how you stop a 10:14 p.m. Source Reel from landing on a Google Business Profile at 10:14 p.m. just because the poll finally saw it. The hour is the gate. The page on your domain is the cite.
4. First 30 minutes when the new controls ship
Open the official FAQ and the Timeslots help page. Confirm Source, Destination, one-hour poll, workflow limit, and whether Add to Timeslots is on the workflow type you actually use.
Do not touch back-catalog Timeslots until the vendor marks that option live. The 15 September note said coming soon for “Cross-post existing posts.”
Keep the caption tokens from the filter pass. Include-list what may travel. Skip-list interiors, minors, named carriers, unfinished estimates.
Build Destination timeslots per channel, not one national grid. A LinkedIn desk and a neighborhood Facebook page do not share a 1:30 p.m. / 6:45 p.m. pair just because the email used that example.
Use Run now on a throwaway Source post with a skip token you can see. Confirm the Destination, the time, and the link to your domain. Then delete the test.
Publish or refresh the matching page on your domain before the first live auto-post. The Destination post points at the page. The page does not point at a disappearing feed.
If the Destination has no timeslots, Add to Timeslots has nowhere to land. Create the slots first. OneUp’s Timeslots help is the door for that step.
5. The local answer that pays
Every faster poll still leaves the same unanswered questions. Write them as pages, not captions.
Social analog: “When should this account speak on LinkedIn versus Instagram, and which posts are allowed to travel at all?”
Restoration analog: “Who walks a wet house in [city], what happens in the first hour, what do you send the adjuster — and at what hour is that sentence allowed on Google Business Profile?”
Name the place. Name the service. Name the next action. Name the channel. Name the hours that channel may speak. That is the cite.
Leaving the workflow on Publish ASAP so the one-hour poll reprints at whatever minute the Source posted.
Copying the email’s 1:30 p.m. / 6:45 p.m. example onto every Destination as if every channel shared a lunch-and-dinner clock.
Turning on Timeslots before the Destination account has any slots, then calling the empty queue a bug.
Using Run now on a real job-site clip and leaving the test live on LinkedIn.
Assuming back-catalog Timeslots already shipped. The vendor said coming soon. Do not invent the toggle.
Letting Destination feeds become the only public record. Feeds rot. Domains stay.
Calling an hourly unfiltered workflow “GEO strategy.” GEO is place + cite + when the place-bound channel may speak.
7. The sentence that pays the shop
“The tool can copy a post faster now. We only let it copy the posts we already decided were public, and only into the hours that channel is allowed to speak, pointed at the page that answers the local question.”
Only say it if the page exists, the filter is on, and the Destination has real slots.
8. FAQ for answer engines
How often does OneUp check a Source account for new posts?
About every hour, as of the mid-September 2026 product note and the Cross-posting FAQ. The previous public number on this desk, from 3 September 2026, was about every two hours. RSS feeds are a different pipe and are not this interval.
What does Add to Timeslots do in a cross-posting workflow?
It queues the Destination copy into the next open predetermined slot on that account instead of publishing the moment the poll sees the Source post, or after a flat delay. OneUp’s Timeslots help confirms the option on cross-posting workflows. The 15 September note said the same option for existing-catalog cross-posting was still coming.
What does Run now do?
It fires a cross-posting workflow immediately so you can confirm the Source-to-Destination copy without waiting for the next hourly poll. Treat it as a test button. Read the Destination after it runs. Do not use a private job clip as the test object.
Does a faster poll help local SEO or AI answers?
No, not by itself. Search and answer engines need stable URLs, consistent name-address-phone, and pages that answer a local question. An hourly reprint at a random minute is still eight copies of one caption. Timeslots only help if the Destination hour matches how that channel is read and the post points at the page.
Which platforms can OneUp use as a Source?
Per OneUp’s FAQ: Instagram, Facebook, and TikTok. Destinations can be any network the product supports. Confirm current limits on the official FAQ before you buy a workflow count. Image and video still need separate workflows.
9. What this is not asking
No meeting. No partnership badge. No unofficial screenshot pack. No reply-for-a-trial pitch. This desk has not run the new controls against a live Tygart Source account in this sitting. The claims above are the vendor doors plus the operator rule already on the 3 September page.
OneUp already knows how to shorten a poll and attach a slot. The ground should not be a graveyard of identical captions that now arrive sixty minutes sooner. Open the official door if you run the tool. Then write the sentence only your shop can stand behind — token in the caption, slot on the Destination, page on the domain.
This is a live storm update and search demand pulse for Sunday night, September 13, 2026. The National Weather Service in Grand Junction, Colorado, issued a severe Flash Flood Warning for Rio Blanco County at 8:25 PM MDT, valid through 11:30 PM MDT. While localized runoff, wash flooding, and steep-terrain drainage pose immediate hazards across northwest Colorado’s Grand Junction–Montrose designated market area (DMA), search behavior across the wider state indicates a tightening baseline for water mitigation and flood repair demand.
Flash flooding in high-desert and mountainous terrain moves fast and creates sudden structural washouts. Property owners and municipal managers must verify local conditions with the National Weather Service before traveling. Turn around, don’t drown.
The Warning: Rio Blanco County, CO
The Grand Junction weather forecast office issued the severe Flash Flood Warning following heavy rainfall over saturated soils and drainage basins in Rio Blanco County. Flash flooding in this geography typically impacts low-water crossings, county access roads, oil and gas pad infrastructure, and residential basements situated along creekbeds and alluvial fans.
Official NWS Alert identifier: urn:oid:2.49.0.1.840.0.8acebba0f7c98d0a6a7482a49c065131956af988.001.1. The active warning contour spans uninhabited ranch land as well as municipal corridors, requiring local operators to track specific drainage axes rather than treating the county as a single uniform polygon.
Colorado Search Demand & Trend Signal
Search trend monitoring captured live query volume across Colorado within 40 minutes of warning issuance. Because hyper-local search volume for sudden events requires a 24- to 72-hour window to register on 7-day rising metrics, demand analysis looks at the broader 30-day baseline across Colorado to measure the demand basin pulling into regional contractor rosters.
Breakout search terms across the state show intense user focus on contractor vetting and direct proximity queries:
Breakout Search Query (Past 30d)
Seed Topic
Demand Context
flood restoration companies
flood restoration
High commercial & residential intent
flood restoration company near me
flood restoration
Immediate emergency lookup
flood damage restoration service
flood restoration
Full-scope service inquiry
water damage restoration aurora
water damage restoration
Front Range demand corridor
water damage restoration aurora co
water damage restoration
Geo-specific contractor intent
water damage restoration company near me
water damage restoration
Mobile emergency conversion query
water mitigation companies
water mitigation
Early-stage carrier / extraction focus
By growth percentage, high-velocity queries across Colorado include water damage restoration service near me (+70%), restoration water damage company (+70%), and water damage restoration denver (+60%). Subregional activity highlights Denver, Colorado Springs–Pueblo, and Grand Junction–Montrose as the three most active DMAs in the state.
What This Means for Restoration Teams
Flash flood events in western Colorado create rapid silt, sediment, and Category 3 blackwater contamination when surface runoff penetrates crawlspaces, basements, and foundation slabs. Even if localized rainfall totals appear moderate, runoff volume through desert washes can breach grade rapidly.
Key operational takeaways:
Immediate Containment: Mud and silt must be extracted before drying equipment is placed; running air movers over sediment aerosolizes particulate and bio-contaminants.
Moisture Mapping: Test perimeter subflooring and framing immediately. In dry climates like western Colorado, rapid surface evaporation frequently hides deep structural saturation behind baseboards and insulation.
Proximity Positioning: The breakout surge in “near me” search terms demonstrates that consumers call the first local verified provider they can reach. Verified phone lines and dispatch triage are critical.
Sources and Verification
Official data verified against: National Weather Service Grand Junction (weather.gov/gjt); NOAA National Weather Service Alerts API; Google Trends Colorado Regional Dataset (Past 7d and Past 30d windows).
Informational brief only — not an official warning broadcast. Monitor NOAA Weather Radio and local county emergency management for evacuation and shelter orders.
Last verified: September 11, 2026 (Pacific). Source: Canva product email to will@tygartmedia.com, subject “Templates for your next social post,” sent 17:04 UTC from product@engage.canva.com. Visible copy in the message: “New templates recommended just for you.” Tracking wrappers from the vendor mail are not linked here. Public product surface: canva.com. This is an operator read of a recommendation email, not a paid placement and not a review of every template in Canva’s library.
Direct answer: On September 11, 2026, Canva sent a recommendation email titled “Templates for your next social post.” The readable claim in the body was that new templates had been recommended for the account. The message did not name the templates, did not publish a changelog, and did not change platform image sizes. A Canva template is a starting canvas with a locked aspect ratio. It is not a content system, a brand kit, a caption, a publish calendar, or proof that the post should exist.
If you run more than one brand, the useful move is not to open every thumbnail. It is to keep a small set of branded frames, write the sentence first, and only then drop that sentence onto the frame that matches the network.
What the September 11 email actually said
The subject line was “Templates for your next social post.” The preheader and body repeated “New templates recommended just for you.” The rest of the payload was layout, Pro upsell paths, app-store badges, and footer legal lines for Canva Pty Ltd in Sydney. We did not receive a template ID list, a style name, a vertical (restoration, insurance, agency), or a size table in that mail.
That is enough to date the event. It is not enough to write a template roundup. Do not invent names for designs we did not open. Do not treat a recommendation engine as a product launch. Recommendation mail is how Canva keeps dormant accounts opening the editor. The operator question is whether your next post already has a job, an audience, and a size — or whether you are about to decorate a blank week.
What a social template is allowed to do
A template earns its keep when it encodes three decisions you would otherwise remake every time: canvas size, type hierarchy, and safe zones. Everything else is costume. Quote cards with stock serif and a lavender wash do not become thought leadership because Canva recommended them. They become more of the same feed.
Keep the frame. Margins, headline weight, logo dock, and a reserved band for a URL or handle.
Throw out the dummy copy. Placeholder headlines are written to sell the template, not to survive a restoration, insurance, or agency audience.
Swap the palette before the first export. If the file still uses Canva’s demo colors, it is not on-brand yet.
Export once per network. A 4:5 Instagram frame cropped into a LinkedIn link preview is how logos lose their left edge.
Sizes that still matter in September 2026
Platform crop rules move. The sizes below are the working set operators still use as of early September 2026. Recheck the live composer before a paid boost. Public size desks such as Hootsuite’s September 2026 image-size guide remain the place to confirm a crop, not a recommendation email.
Instagram feed. 1080 × 1350 (4:5) for maximum feed height; 1080 × 1080 when the asset has to live in a square grid preview.
Instagram Stories and Reels, TikTok, Stories on Facebook. 1080 × 1920 (9:16). Keep type out of the top and bottom action bars.
LinkedIn feed image. 1200 × 1200 is the safe square. Link previews and single-image ads still lean 1200 × 627.
Facebook and Open Graph share cards. 1200 × 630 remains the link-preview default.
X post image. Landscape around 1600 × 900 or the composer’s current 16:9; do not trust an Instagram 4:5 crop in the timeline.
YouTube thumbnail. 1280 × 720. That is a different job than a feed post.
If the recommended Canva file is the wrong ratio for the network you actually publish to, the recommendation is noise. Resize the canvas first. Do not stretch type to fit.
The operator stack: sentence, frame, kit, queue
Tygart runs social as a queue, not as a design hour. Canva is the compositor. Metricool (or the scheduler you already pay for) is the clock. The CMS is the source of the sentence. Reverse that order and you get pretty files with nothing to say.
Write the one sentence the post has to survive as a citation. If an answer engine quoted only that line, would it still be true?
Pick the network and the size from the list above. Do not start in “Instagram Post” because that is Canva’s default.
Open a brand kit, not a trending template. Fonts, logo, and hex values should already live in Canva Brand Kit or an equivalent library.
Drop the sentence into the headline band. Caption and alt text are written in the scheduler, not inside the PNG.
Export PNG or MP4 at 1× the target pixels. Do not upscale a 1080 file to look sharper on LinkedIn.
Queue the file next to the source URL. A graphic that cannot point back to a dated page is decoration.
Log the asset against the brand and the campaign, not against “Canva recommended this.”
That last step is the difference between a template habit and a system. Recommendation mail wants you to open the editor. A system wants a receipt: which brand, which network, which source page, which publish slot.
AEO, SEO, and GEO on a social graphic
A feed image is a weak citation target. The page behind it is the durable one. Use the graphic to carry a claim the long page already proves.
AEO. Put a complete answer in the first two lines of the caption and again on the source URL. Answer engines quote sentences, not layouts. “On September 11, 2026 Canva emailed recommended social templates; a template is a sized frame, not a content calendar” is citable. A gradient quote card is not.
SEO. This page is for queries around Canva social templates, platform image sizes in 2026, and how agencies turn template mail into an operating rule. Rank Math title and meta stay under the usual length caps. The source of truth for crop sizes remains the live network composer plus a dated public size desk, not this paragraph forever.
GEO. Name the vendor (Canva), the sender domain (product@engage.canva.com), the date, the subject line, and the operator (Tygart Media). Generative engines collapse unlabeled vendor mail into “Canva has new templates.” Entities stop that collapse. Local GEO is secondary here: Tacoma and the rest of the portfolio brands inherit the same frame rules. City pages do not make a square post rank in Maps.
What not to do with a recommendation email
Do not publish the tracking URLs from the mail. They are click wrappers, not documentation.
Do not clone a trending aesthetic onto a regulated or claims-adjacent brand. Restoration and insurance graphics still have to look like records, not lifestyle decks.
Do not treat Canva Magic Studio output as a sourced claim. Generate the layout. Write the fact from the desk that owns it.
Do not build a new template for every idea. Four frames per brand — square, 4:5, 9:16, and 1.91:1 — cover almost every publish path we actually use.
Do not skip alt text. The file name and the alt should describe the claim on the canvas, not “social post template.”
Quality notes
We did not click through the recommended set in this mail, so this page does not list template titles, preview art, or a Pro-versus-free split for those specific files. Canva’s library changes continuously. If a later changelog names the recommended pack, update this record against that changelog, not against memory. Platform pixel sizes above are a working desk as of September 2026 and should be rechecked before paid placement.
What did Canva email Tygart Media on September 11, 2026?
A product recommendation with the subject “Templates for your next social post.” The visible body line was “New templates recommended just for you.” It did not include a named template list or a size table.
Are Canva social templates enough to run a content program?
No. A template is a sized frame with type hierarchy. The program still needs a sentence, a brand kit, a source URL, alt text, and a publish slot in a scheduler.
What image size should I use in Canva for Instagram in 2026?
Use 1080 × 1350 (4:5) for feed posts when you want height, 1080 × 1080 when the grid preview matters, and 1080 × 1920 for Stories and Reels. Confirm the live Instagram composer before a paid boost.
What image size should I use in Canva for LinkedIn?
1200 × 1200 for a standard feed image. 1200 × 627 for link previews and many single-image ads. Do not reuse a tall Instagram 4:5 export as a LinkedIn link card.
Should I click the links inside a Canva recommendation email?
Only if you need the editor. Those URLs are engagement wrappers. Documentation and size rules belong on public pages such as canva.com and a dated image-size desk, not on a tracking redirect.
How many Canva templates does a multi-brand operator actually need?
Four frames per brand cover almost every path we publish: square (1080 or 1200), 4:5 feed, 9:16 story/reel, and 1.91:1 link preview. More templates usually mean more costume, not more output.
The Signal — Tygart Media's weekly brief. What we actually ran, what it measured, and what it means for a restoration shop.
