Day 2: I Stopped Treating SEO Like Marketing (It’s Ops)
Yesterday I shared why I built Vistrify: SEO usually fails because execution is too heavy for a solo founder.
Today I want to go one layer deeper, because this is the mindset shift that made everything click for me:
SEO is not marketing. It is operations.
And if you run it like operations, it starts working.
Why most founders bounce off SEO
The typical “SEO plan” looks like motivation, not a system:
“I’ll write 2 posts a week.”
“I’ll do keyword research this weekend.”
“I’ll publish consistently from now on.”
Then life happens.
Support tickets happen.
A feature breaks.
A customer churns.
You change the homepage.
You rewrite pricing.
You do outreach.
And SEO is the first thing that gets sacrificed because it is never urgent.
That is the trap.
SEO does not feel urgent until you are out of options.
What operations thinking changes
Operations is boring on purpose.
Operations means:
Clear inputs
Repeatable steps
Predictable output
Low cognitive load
A default cadence that survives bad weeks
If you treat SEO like operations, your goal becomes:
“Can I produce publishable drafts reliably, with minimal effort, every week?”
Not: “Can I write a masterpiece today?”
Not: “Can I find the perfect keyword?”
Just: reliable throughput.
The workflow that actually survives founder life
Here is the simplest SEO workflow I have seen that does not collapse:
Start from your product reality
Not generic “best keywords.” Keywords that match what you sell.Generate a content plan once, then reuse it
Stop reinventing topics every week.Create a draft fast, then edit
Drafting is the bottleneck. Editing is manageable.Publish with a minimum standard
Good enough, consistent, and aligned beats perfect and rare.
This is why Vistrify is built the way it is: URL → plan → long-form drafts.
It is not “AI magic.”
It is reducing the friction in the pipeline.
The uncomfortable truth about SEO content
Most founders do not need more ideas.
They need fewer decisions.
SEO content dies from decision fatigue:
Which topic first?
Which angle?
How long?
What structure?
What headers?
How do I connect it to my product?
Is this even worth publishing?
When you remove those decisions, publishing becomes a weekly habit instead of a heroic effort.
What I’m optimizing in Vistrify next
If SEO is ops, then the product is a machine.
And a machine is judged by output quality and reliability.
So my current focus is:
Better topic clustering (less randomness, more structure)
Drafts that match search intent more tightly
Stronger product alignment inside the content (without turning it into spam)
Making “draft → publish” faster for founders
A small challenge (that actually works)
If you are an indie founder and you want organic growth, try this for 7 days:
Publish one post per day or every two days
Do not aim for perfection
Aim for consistency and relevance
Track: impressions, clicks, and what keywords start showing up in Search Console
The goal is not rankings in 7 days.
The goal is momentum and signal.
Because once you see signal, you can iterate.
That’s Day 2
SEO is not a creative hobby.
It is a production line.
If your workflow is heavy, it will not run.
If your workflow is light, it becomes inevitable.
Tomorrow I’ll share the exact rule I use to decide whether a keyword is worth writing about as a tiny product.
If you’re building for SEO too, what part of the pipeline is your biggest blocker right now: planning, writing, or publishing?
Mateusz, this is genuinely one of the clearest explanations of the SEO mindset shift I've read in a while.
"SEO is not marketing. It is operations."
That single line reframed how I think about what I've been doing with my own project, FontPreview. I launched a month ago, wrote 9 guides, and somehow got to 1,400 users. I thought I was just "writing consistently," but reading this — I realize I accidentally built an ops workflow without knowing it.
I picked topics I actually knew (font licensing, serif psychology) and just... wrote. No agonizing over keywords. No decision fatigue. Just "what do designers actually search for at 2am?" and then answered it.
The part about decision fatigue hit hard:
"When you remove those decisions, publishing becomes a weekly habit instead of a heroic effort."
That's exactly it. The weeks I overthought topics, I published nothing. The weeks I just wrote what I knew, something went live.
Question for you — when you say "drafts that match search intent more tightly," how do you validate intent before writing? I've been using the "search for it myself and see what's already ranking" method, but curious if you have a more systematic approach.
Also, love the 7-day challenge. Might actually try that next week — one post every two days, no perfectionism allowed.
Looking forward to Day 3.
Love this, and huge congrats on 1,400 users for FontPreview in a month — that’s real traction.
And yes, what you described is exactly the ops model in practice: low-friction publishing around real user questions.
On search intent validation: I still do manual SERP checks, but with a simple scoring system before I write:
Intent pattern: what are top results mostly doing (guide, template, comparison, tool page, etc.)?
Promise match: what outcome do those pages promise in the first screen?
Product fit: can I naturally connect that intent to a real next step in my product?
Go/no-go: if I can’t define “query → intent → angle → CTA” in one sentence, I skip it.
So it’s still “search it myself,” just standardized so the decision is fast and repeatable.
If you run the 7-day challenge, I’d love to hear your before/after signal in Search Console.
Really appreciate that! 🙏 And thanks for sharing your scoring system — the "query → intent → angle → CTA" framework is gold. I'm going to try the 7-day challenge next week and will definitely report back. Quick question: when you do manual SERP checks, do you have a go-to tool or just raw Google?
I use plain Google first (incognito, logged out, target country) to avoid personalization, then I sanity-check with GSC/Ahrefs for volume and keyword variants. For intent, I mainly read the top 5 results, titles/H1 patterns, and PAA. If 4/5 pages match one intent, I treat it as clear and move forward.
Thanks for sharing your workflow — super helpful. The "incognito + logged out" trick is something I forget to do sometimes, but it makes so much sense to avoid personalization bias.
I've been doing something similar with my own tool FontPreview — before writing any guide, I search for the topic myself and see what's already ranking. The "if 4/5 pages match one intent" rule is gold. I'm definitely adding that to my process.
Quick question: when you check PAA (People Also Ask), do you find those questions are usually good content ideas on their own, or do you use them more for structuring existing topics?
Appreciate you taking the time to explain!
Appreciate this, and great question.
I use PAA mostly for structuring existing topics (H2s, objections, next-step questions).
I treat a PAA question as a standalone post only if it has:
clear intent on its own,
enough depth for a full answer, and
natural product fit.
So default = structure; standalone = only when it passes those checks.
This is really helpful — thanks for breaking down your thought process. The "clear intent on its own" check is such a simple but smart filter. I've definitely fallen into the trap of stretching a PAA question into a full post just because it existed, not because it deserved one.
For FontPreview, I've been using PAA mostly for blog post structure too — especially for topics like "what fonts go together" or "are Google Fonts free for commercial use." Those questions naturally fit as H2s under a bigger umbrella.
The standalone approach makes a lot of sense for questions with real search depth. Have you seen better engagement with standalone PAA posts vs structured ones? Curious what the data says.
Great question. Still early data on my side, but the pattern is pretty consistent:
Structured PAA sections usually win on reach (more impressions).
Standalone PAA posts usually win on intent quality (better CTR/conversion) when the query is narrow and high-intent.
So my default is: use PAA for structure, then split into standalone only if it can carry a full answer and a natural CTA without filler.
My quick filter is still: can I define query -> intent -> angle -> CTA in one sentence? If yes, standalone. If not, keep it as an H2.
This is such a clean framework — especially the "query → intent → angle → CTA in one sentence" test. I'm going to borrow that.
For FontPreview, I've noticed a similar pattern. Broad questions like "what are Google Fonts?" work better as H2s within a larger guide. But narrow ones like "are Google Fonts free for commercial use?" can absolutely carry a standalone post — because the intent is clear (someone about to make a legal decision) and the CTA (check the license) writes itself.
The reach vs intent tradeoff is real. Structured content brings people in, standalone converts them.
Do you ever find that some standalone PAA posts end up cannibalizing your structured content? Or do they tend to attract different searchers?
I think you have a solid point on just producing something consistently then iterating. Sometimes u have no idea what will work and produce reveneue/leads until u do it, see whats working then iterate.
You nailed it. Early SEO is basically experiment loops: ship consistently, watch what gets impressions/clicks/leads, then double down on what shows signal. I’d rather publish 7 good-enough posts and learn than spend 2 weeks on one “perfect” post.
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?
Thanks, appreciate it. Right now I’m doing founder-led acquisition: building in public (Indie Hackers/X), sharing practical SEO workflow content, and direct outreach to indie founders who already feel the content bottleneck. For feedback, I’m prioritizing quick onboarding calls + follow-ups after first draft generation, then shipping based on repeated friction in the flow (URL → plan → draft → publish).
I appreciate your openness about the challenges of distribution. That topic often doesn’t receive enough attention.
I've observed that for many early founders, the real difficulty lies not in generating ideas but in maintaining a consistent content flow.
Out of curiosity, have you considered engaging in conversations on Reddit instead of solely publishing standalone posts? Sometimes, participating in existing threads where the issue is already being discussed can eliminate a lot of the friction.
Appreciate this, and I agree.
Consistency has been harder than idea generation, so I’m shifting from “big standalone posts” to more regular participation in existing conversations. I’ve started testing a mix of build-in-public updates plus helpful replies in threads where freelancers are already talking about late payments.
If you have a few Reddit communities/threads you think are especially relevant, I’d genuinely appreciate pointers.
Really glad you’re leaning into participation instead of just standalone posts, that’s usually where Reddit starts to feel less like broadcasting and more like distribution.
Since you’re targeting freelancers dealing with late payments, I’d keep an eye on places like r/freelance, r/Entrepreneur, r/smallbusiness, and even some niche creator subreddits, depending on your angle. But honestly, the real gold isn’t the subreddit, it’s the specific threads where someone is actively frustrated.
For example, when someone posts something like “Client hasn’t paid me in 45 days, what should I do?”, that’s a much stronger entry point than a general product mention. Those conversations already have intent baked in.
One thing that tends to work well for tools in your space is sharing your own workflow or process first, how you reduced payment friction, and then naturally mentioning the product as part of that system, instead of leading with the product itself.
If you’d like, I can take a look and point you to a few current threads where your audience is already talking about this.