Introduction
If you have spent the last six months reading about AI in SEO, you have probably noticed a familiar pattern. The articles describe enterprise teams running ambitious AI-assisted operations, the case studies feature companies with eight-person SEO departments, and the implicit reader has a Jira queue and a quarterly OKR review. For a Fort Wayne dental practice with a part-time marketer or a Northeast Indiana home-services owner who handles their own content, those frameworks read as aspirational rather than usable.
That is the problem worth solving this week. On April 24, Search Engine Land published a piece by Travis Tallent on three AI-driven SEO frameworks — AI SEO City, SOAR, and RISE — that he has used inside Fortune 100 SEO teams. The frameworks are good. They are also, on first read, written for a much larger operation than most small businesses run. The translation work — which framework fits which size of small business, what to skip, and where the failure modes are — is what this post does.
We have field-tested these frameworks across 1-person, 3-person, and 10–15-person operations in Northeast Indiana. All three are usable at small-business scale, but only one fits a 1-person operation. Picking the right framework matters more than executing the wrong one perfectly.
Key Takeaways
- Travis Tallent's three AI-driven SEO frameworks — AI SEO City (organizational alignment), SOAR (decision filter for what to automate), and RISE (initiative prioritization) — were published in Search Engine Land on April 24, 2026 and are written for enterprise teams
- Only the SOAR framework is genuinely runnable by a 1-person owner-operator; AI SEO City needs a marketing lead, and RISE needs at least a part-time SEO contributor
- Tallent reports AI is “helping people save about 4 hours per week” — about 200 hours per year, or five working weeks
- A separate Search Engine Land piece on automating SEO busywork lists eight automatable tasks with realistic per-task time savings (10–20 minutes each)
- Common failure modes: over-automating, skipping human review, treating prompts as static, and confusing “AI did it faster” with “AI did it better”
- A 90-day adoption ramp: month 1 pick one framework and one surface, month 2 measure baseline, month 3 expand or kill
- Fort Wayne and Northeast Indiana operating realities (no marketing department, owner-operator decisions, $500–$5k/month budgets) shape which framework to start with
What Are the Three Frameworks?
Tallent's Search Engine Land article lays out three distinct frameworks. They sit on top of each other in the order an organization grows into them, but they are independently usable. Here is the faithful summary of each, with a small-business framing in the second sentence.
AI SEO City — organizational alignment. Tallent's first framework uses a city metaphor. The “foundation” is technical SEO; the “core structure” is content hubs and UX; “curb appeal” is off-site SEO; the “expanded city” includes external platforms (TikTok, Reddit, YouTube, Amazon); and the SEO team acts as “city planner” with budget advocacy and roadmap authority. Each major platform becomes a “building” with designated ownership, KPIs tied to business outcomes, AI-enhanced workflows, and quarterly roadmaps. The honest small-business read: this framework is about coordination across multiple owners. If your business has one person doing all of it, the framework is overhead, not infrastructure.
SOAR — decision filter for AI adoption. SOAR stands for Streamline the Basics, Orchestrate Your Team, Automate Monotony, Reposition Focus. It is a four-step decision filter for which workflows deserve AI automation versus which should stay human. Tallent argues you cannot automate broken processes, and he cites McKinsey's State of AI report for the finding that organizations capturing the most AI value had already digitized their foundational processes before automating. The honest small-business read: this is the one a 1-person operation can run. Streamline what you do manually first; then automate what remains repeatable.
RISE — initiative prioritization. RISE stands for Reach, Intent, Scale, Execution. It is a four-step prioritization framework Tallent uses to pressure-test whether a proposed SEO initiative deserves resources. Reach quantifies the upside; Intent aligns with user objectives; Scale ensures the initiative compounds (rather than being a one-off tactic); Execution translates strategy into tickets in Jira, Asana, or your project tool. The honest small-business read: this requires enough volume of competing ideas to be worth filtering. A one-person operation has 2–3 ideas at any time and does not need a four-stage filter. A 5–15 person operation does.
A useful expert framing from a parallel Search Engine Land piece on why topical authority isn't enough supports why these frameworks matter now: AI engines are increasingly selecting cited sources by “topical position” — not just coverage. The frameworks above are different mechanics for ensuring you are repeatedly producing position-earning work rather than ad-hoc content.
Which Framework Fits Which Size of Small Business?
The answer depends on how many people in your business actually touch SEO work. Here is the honest mapping based on our field experience and the source article's implicit assumptions.
| Operation size | Best primary framework | Skip / defer | Realistic weekly time |
|---|---|---|---|
| 1-person owner-operator | SOAR | AI SEO City, RISE | 2–4 hours |
| 2–5 person small business with part-time marketer | SOAR + abbreviated RISE | Full AI SEO City | 4–8 hours |
| 5–15 person business with marketing lead | All three, layered | None | 10–20 hours |
The honest note: the prompt-library and automation-first version of SOAR is the only one a true 1-person operation should attempt. The other two frameworks assume a person whose dedicated job is SEO operations. If you do not have that person, AI SEO City becomes a Gantt chart you maintain instead of doing work, and RISE becomes a filter applied to ideas you are not going to execute anyway.
For 2–5 person Northeast Indiana businesses with a part-time marketer, SOAR is still the primary tool, but the Reach and Intent steps of RISE are usable as a lightweight pre-filter on what to put through SOAR in the first place. Skip the Scale and Execution steps unless you have a content-production cadence that can support them.
For 5–15 person operations with a marketing lead — which describes a small fraction of Fort Wayne service businesses but exists in some manufacturing and B2B-services categories — all three frameworks are layered. AI SEO City sets organizational coordination, SOAR governs which workflows get automated, and RISE filters the initiative queue. The annual time investment is meaningful but the compounding effect is real.
SOAR for the One-Person Operation
This is the deepest section because SOAR is the framework most Fort Wayne and Northeast Indiana small businesses can actually run. Here is the version that fits an owner-operator's real schedule.
Streamline the Basics. Before you automate anything, document what you currently do manually. Write down the four or five SEO tasks you actually perform each month — keyword research, on-page edits, FAQ updates, GBP posts, performance review. For each, write the steps in plain English in a single text file. This sounds tedious. It is also the step that makes everything downstream possible. Tallent notes — citing McKinsey — that organizations capturing the most AI value had already digitized their foundational processes before automating. For a small business, “digitized” just means “written down clearly.” If the steps are not written, the prompts will not be repeatable.
Orchestrate Your Team. For a true 1-person operation, this step is mostly internal — you are orchestrating yourself. Set a weekly cadence: 30 minutes Monday for performance review, 90 minutes mid-week for content production, 30 minutes Friday for measurement. The point is consistency, not heroics. For a 2–5 person team, this step also covers the handoff from owner to part-time marketer, including QA ownership, publishing governance, and a defined review path. Without these explicit handoffs, AI-generated work tends to ship without review and create the over-automation failure mode we will cover below.
Automate Monotony. This is where the AI use cases live. The Search Engine Land piece on automating SEO busywork lists eight tasks with realistic time savings: content calendar (saves about 8 hours per quarter), keyword research (15 minutes per page), internal linking suggestions (10 minutes per page), content outlines and briefs (20 minutes per ticket), brand-standards compliance, data validation, metadata and schema generation (10 minutes), and formatting (15 minutes per page). For a 1-person operation, start with three: keyword research, internal linking, and metadata. Those three return the most time per dollar of prompt-engineering investment. Automating beyond three means you are spending more time engineering prompts than doing SEO.
Reposition Focus. What you do with the saved time matters more than the saving itself. Tallent says AI is “helping people save about 4 hours per week” — about 200 hours per year, or five working weeks. The reposition step asks where those saved hours should go. For a small business, the highest-leverage repositioning is into customer interviews and original content. AI compresses the busywork; it does not replace the parts of SEO that require talking to actual Fort Wayne customers and writing things AI does not already know.
A specific operational note: the prompt-engineering pattern that fits this framework is the one Search Engine Land covered in an April 9 piece on AI prompts for ad campaigns — start with one or two prompts, refine the outputs iteratively, and “build from there.” The same pattern applies to SEO prompts. Treat the prompt library as a versioned asset that improves over time. We covered the underlying repeatability pattern in Claude Skills for repeatable PPC systems, which is the same pattern applied to a different surface.
RISE for the 2–5 Person Small Business — Abbreviated
If you have a part-time marketer or a marketing-lead-and-an-owner setup, the abbreviated RISE pre-filter takes about 30 minutes per week and saves substantially more time than that downstream by killing bad ideas before they consume production capacity.
Reach (10 minutes). For each new SEO idea on the table, estimate three numbers. What is the addressable search demand for the target keyword cluster? What is your current visibility share against the top three competitors? What is the realistic incremental traffic if you ranked in position 3? You do not need precise numbers — order-of-magnitude is enough. Tallent's own framing in the Search Engine Land article is direct: “If you can't articulate the business upside in numbers, it doesn't move forward.” The same discipline applies at small-business scale, just with smaller numbers.
Intent (10 minutes). Map the proposed work to actual user objectives. Is this awareness, comparison, or conversion content? What query patterns does the target audience actually use? Are AI Overviews appearing on those queries? We covered this last variable in our work on intent gap analysis in Search Console — small businesses often skip the Intent step and end up writing well-optimized content for queries the customer never actually runs.
Scale and Execution — skip for now. For a 2–5 person operation, the Scale step (modular content frameworks, reusable schema logic) and the Execution step (project-management tickets with formal acceptance criteria) are honest overkill. Use a shared Notion or Google Doc with three columns — idea, current status, next action — and revisit weekly. Ship-or-skip is the only meaningful state at this scale.
The discipline RISE adds even in this abbreviated form is killing low-Reach, low-Intent ideas before they get built. Most small-business SEO time is wasted on ideas that scored low on both filters but felt productive at the time.
AI SEO City — Honest Caveat for Most Small Businesses
We are flagging this framework specifically to advise against starting here.
AI SEO City is genuinely valuable for organizations that already have multiple people coordinating across SEO surfaces — a technical SEO contributor, a content lead, a paid-media counterpart, an in-house developer. The “city planner” coordination role is real value-add when there are buildings to coordinate. For most Fort Wayne small businesses, those buildings do not yet exist. Spending Q1 building a city plan for a business that has not finished its first SEO surface is a classic small-business failure mode — designing the org chart for the company you wish you were while underexecuting the company you are.
The single useful piece of AI SEO City for a 1–5 person operation is the platform-priority decision: which “buildings” deserve attention first? For most service-business categories in Northeast Indiana, the answer is in this order: Google organic and AI Overviews first, Google Business Profile second, ChatGPT and Perplexity citation work third, YouTube fourth, Reddit and TikTok later. We argued for this ordering in our Fort Wayne SEO foundation post, and the prioritization holds.
If you have grown to 10–15 people and the platform-coordination problem is now real — multiple owners, multiple campaigns, conflicting briefs — that is the moment to revisit AI SEO City as a coordination tool. Until then, skip it.
Fort Wayne and Northeast Indiana — Picking a Framework
For NE Indiana small businesses across HVAC, dental, legal, and home-services, the framework selection plays out predictably based on operation size. Here is the practical guidance we give clients.
A 1-person owner-operator HVAC company in Auburn or Garrett should run SOAR with a tight three-prompt automation library — keyword research, internal linking, and metadata. The Streamline step takes one Saturday morning to write down the four monthly SEO tasks. The Orchestrate step is a weekly 30-minute calendar block. The Automate step uses ChatGPT or Claude (free tier is fine for these three prompts). Reposition the saved 2–4 hours per week into customer interviews and reviews. Total realistic weekly investment: 2–4 hours.
A 3-person dental practice in Fort Wayne with a part-time marketer should run SOAR plus the abbreviated Reach-and-Intent steps of RISE. The marketer owns the 30-minute weekly RISE filter; the owner owns the Streamline and Reposition decisions. Skip AI SEO City entirely. Total realistic weekly investment: 4–8 hours including the marketer's time.
A 10-person home-services company with a marketing lead and an in-house web contributor should consider all three frameworks layered. AI SEO City for cross-surface coordination, SOAR for which workflows the marketing lead automates versus owns manually, RISE for the initiative queue. Total realistic weekly investment: 10–20 hours across the team. We covered the parallel competitor-research lane in our Fort Wayne AI competitor analysis playbook, which integrates with the Reach step of RISE for businesses at this scale.
A consistent piece of feedback from Northeast Indiana clients: the frameworks become genuinely useful only after about six weeks of consistent execution. The first month feels like overhead. The second month, the prompt library starts producing time savings; by month three, the cadence has compressed an SEO task that used to take a half-day into 90 minutes. Plan for the trough.
Common Failure Modes
The Search Engine Land piece on automating SEO busywork identifies three core problems automation cannot solve: broken systems, incomplete assets, and lack of resources. Translated to small-business SEO operations, the failure modes look like this.
Over-automating. Trying to automate everything in month one is the most common mistake. The prompt engineering eats more time than the manual work saved, and the output quality drops. Pick three prompts to start. Add a fourth in month two only if the first three are demonstrably working.
Skipping human review. The Search Engine Land automation piece recommends “let the intern (or AI) do 70% of the work, like research and a rough draft. Then complete the final 30%.” That last 30% is non-negotiable. AI-generated SEO work that ships without owner review is how brand voice degrades, citations get fabricated, and metadata starts misrepresenting the business. Our ChatGPT citations analysis shows that citation-worthy content is precisely the content that has had a competent human do the final pass.
Treating prompts as static. A prompt that worked in January 2026 will degrade by July as model behavior changes and the underlying SEO landscape shifts. Version your prompts. Re-test them quarterly against the same baseline output. The Search Engine Land prompt-engineering piece frames this as iterative refinement; for small businesses, the simplest version is a quarterly 30-minute prompt-review session.
Confusing “AI did it faster” with “AI did it better.” This is the failure mode that sneaks up on owners who succeed at the first three. Speed and quality are different variables. AI-generated content can be faster and worse, and the worse-but-faster pipeline produces a bigger-but-weaker content portfolio that gets cited less. Track citation share, not output volume.
A fifth failure mode worth naming, because we see it in Northeast Indiana: confusing the framework with the work. AI SEO City, SOAR, and RISE are scaffolding. They make the underlying SEO work — content production, technical fixes, entity profile, schema, Google Search Console hygiene, Schema.org implementation — easier to coordinate. They do not replace it. A perfectly-run SOAR cycle that produces no actual published content is a process accomplishment, not a business outcome.
A 90-Day Adoption Ramp for Small Businesses
If you are starting from zero, this is the ramp we recommend. It is conservative on purpose. The frameworks reward consistency more than ambition.
Month 1 — Pick one framework and one surface. For a 1-person operation, this is SOAR applied to your single highest-leverage SEO surface (usually your service pages or your top-three blog posts). For a 3-person operation, this is SOAR plus abbreviated RISE applied to the same. Document the four or five tasks you do manually. Pick three to prompt-automate. Set the weekly cadence. Do not add anything else this month.
Month 2 — Measure baseline. Track three metrics over the month. First, hours per week spent on SEO work. Second, citation appearance — run 10–15 of your highest-priority queries through Google AI Mode and ChatGPT once a week and record whether your domain appears as a cited source. Third, organic traffic to your service pages or target posts. Do not change the framework this month. Just measure. Most owners want to optimize; the discipline is to gather a clean baseline first.
Month 3 — Expand or kill. Compare month-2 metrics to your month-1 baseline. If hours per week dropped and citation appearance held or rose, expand: add a fourth automated prompt, add a measured surface, or add the RISE pre-filter if you skipped it. If hours per week dropped but citation appearance fell, kill the most aggressive automation and restore human review on that surface. If hours per week did not drop, your prompt library is not yet returning time — refine the existing three prompts before adding any new ones.
After 90 days, the right next step depends on your operation size. A 1-person operation should plateau and stay there — adding more frameworks creates overhead without compounding benefit. A 3-person operation can layer in the full RISE filter in month four. A 10–15-person operation can add AI SEO City as a coordination tool in month four. We covered the broader content-cadence parallel work in marketing automation workflows for small business, which sits naturally alongside SOAR adoption.
Where This Fits in Our Work
Most Northeast Indiana clients we work with are 1–5 person operations, which means SOAR is the framework we set up most often. Our SEO service and Answer Engine Optimization service include the prompt-library setup, the weekly cadence design, and the quarterly prompt-review session as standing work. Our AI Solutions service handles the deeper automation and integration work for 5–15 person operations where AI SEO City actually applies. The right starting point depends entirely on operation size — picking SOAR when you should be running RISE wastes time, and picking AI SEO City when you should be running SOAR wastes more. We also lean on our Answer Engine Optimization guide as the underlying entity-and-citation foundation each framework sits on top of.
The principle that holds across operation sizes is that the framework is the scaffolding, not the building. Owners who get traction with these frameworks are the ones who build the underlying SEO work — original content, customer-interview-driven pages, technical entity work, schema, citation-worthy data — and use the framework to coordinate it. Owners who run the framework without the underlying work tend to plateau in month two and quietly abandon the framework in month four. The work is the work; the framework just makes it scale.
Pick the Right SEO Framework for Your Operation Size
Button Block sets up SOAR for owner-operators, abbreviated RISE for small marketing teams, and the full layered approach for 10–15 person operations across Northeast Indiana. We can help you pick the framework that matches your team — and skip the ones that would just become overhead.
Frequently Asked Questions
- Which framework should a 1-person Fort Wayne small business start with?
- SOAR. It is the only one of Tallent's three frameworks designed to run with a single decision-maker. AI SEO City assumes multiple owners coordinating across surfaces; RISE assumes enough volume of competing ideas to need a four-stage filter. Most owner-operators in Northeast Indiana have neither. Streamline what you currently do manually, automate three repeatable tasks, and reposition the saved 2–4 hours per week into customer interviews and original content.
- How long until I see results from running SOAR?
- Plan on six to eight weeks before the time savings become real. The first month is mostly overhead. The prompt library starts saving time in week 4–5; by week 8, routine SEO tasks compress meaningfully. Citation-share movement takes longer — typically 8–12 weeks of consistent execution before AI engines start reflecting the cumulative work.
- What three SEO tasks should I automate first?
- Keyword research, internal linking suggestions, and metadata generation. The Search Engine Land piece on automating SEO busywork reports approximate per-task savings of 15 minutes per page on keyword work, 10 minutes per page on internal linking, and 10 minutes per page on metadata. Across a typical small-business publishing cadence (4–8 pages per month), that is two to three hours saved per month from a single hour of prompt-engineering setup. Higher-leverage automation (content drafting, brand-voice work) requires a larger upfront investment and is harder to get right.
- When does it make sense to add the RISE framework?
- When you have more SEO ideas than capacity to execute them. For most 1-person operations that is 12–18 months in, after the SOAR cadence is producing reliable output. For a 3-person operation with a part-time marketer, the abbreviated Reach-and-Intent pre-filter is usable from month two — the marketer needs an objective filter to defend prioritization decisions back to the owner. The full Scale-and-Execution steps are unnecessary until you have at least one dedicated SEO contributor and a project-management tool you actually use.
- Should a Fort Wayne small business build AI SEO City?
- Almost certainly not. The framework is a coordination tool for organizations with multiple SEO contributors across multiple surfaces (organic, GBP, social, video, paid). Most Fort Wayne small businesses have one or two people doing all of those, in which case AI SEO City becomes overhead. The single useful piece — the platform-priority decision — is well covered in our Fort Wayne SEO foundation post and does not need the city metaphor to be actionable.
- What is the most common mistake small businesses make when adopting AI SEO frameworks?
- Over-automating in month one. The temptation is to build a prompt library covering eight or ten tasks immediately. The actual return is much higher when you start with three prompts, refine them for two months until they reliably produce reviewable output, and only then expand. Owners who skip this discipline end up spending more time engineering prompts than doing SEO, and the output quality drops below what they were producing manually.
- How do I know if AI is making my SEO better or just faster?
- Track citation share, not output volume. Run 10–15 of your highest-priority queries through Google AI Mode, ChatGPT, and Perplexity once a week and record whether your domain appears as a cited source. If output volume rises but citation share stays flat or falls, the automation is producing more, weaker content. If output volume rises and citation share rises with it, the automation is genuinely working. Speed without quality is a problem, not a win.
Sources & Further Reading
- Search Engine Land: searchengineland.com/ai-driven-seo-frameworks-475438 — 3 AI-driven SEO frameworks: AI SEO City, SOAR, and RISE (Travis Tallent, April 24, 2026)
- Search Engine Land: searchengineland.com/automate-seo-tasks-busywork-475359 — 8 SEO tasks to stop doing manually (April 24, 2026)
- Search Engine Land: searchengineland.com/use-ai-prompts-generate-better-ad-campaigns-473942 — How to use AI prompts to generate better ad campaigns (April 9, 2026)
- Search Engine Land: searchengineland.com/why-topical-authority-isnt-enough-for-ai-search-474250 — Why topical authority isn't enough for AI search (April 14, 2026)
- McKinsey & Company: mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai — The state of AI report on enterprise digitization and automation
- Schema.org: schema.org — Structured data reference for entity, FAQ, and article markup
- Google: developers.google.com/search — Google Search Central technical SEO documentation
- Google: support.google.com/webmasters — Google Search Console help and Performance report documentation