# SEO & AI Visibility for SaaS > A practical, evidence-led course for building discoverability across search engines and AI answers—without chasing shortcuts or confusing mentions with business growth. - Author: Blogged Editorial Team - Audience: SaaS founders, marketers, and lean content teams - Access: Free and open; no login, quiz, or certificate - Course URL: https://blogged.dev/courses/saas-seo-ai-visibility - Published release: 2026-09-03T10:27:59.383Z ## Module 1: Build the discovery model Connect search and AI discovery to the customer journey and commercial outcomes. ### Lesson 1: How SaaS discovery works now URL: https://blogged.dev/courses/saas-seo-ai-visibility/how-saas-discovery-works Outcome: You will map a prospect's question from first discovery to a measurable product action. ## One system, several interfaces A SaaS buyer can discover you in a search result, an AI-generated answer, a community thread, a comparison page, or a colleague's link. These interfaces look different, but they usually depend on the same underlying assets: crawlable pages, clear claims, useful evidence, recognizable entities, and links that explain how ideas relate. Treat **SEO** as the practice of making useful pages understandable and eligible for search. Treat **AI visibility** as the chance that an AI system retrieves, understands, cites, or recommends those pages. Neither is a separate content channel. Both sit upstream of the same evaluation journey. ## The SaaS discovery chain 1. A real problem creates a question. 2. A discovery system retrieves candidate information. 3. The interface summarizes, ranks, or cites candidates. 4. The prospect validates the claim on your site and elsewhere. 5. A useful next step—tool, demo, signup, template, or article—moves the evaluation forward. 6. Product and revenue data show whether the visit mattered. This chain exposes two common mistakes. Ranking is not the final outcome, and an AI mention is not proof of influence. The durable objective is to become a trustworthy source that earns qualified visits and helps a buyer make progress. ## Build a source of truth before a content calendar List what your company can prove: product capabilities, limitations, ideal use cases, integrations, pricing rules, customer evidence, and terminology. Assign an owner and freshness date to each important fact. Then connect research and production to that governed knowledge. This reduces contradictions across product pages, articles, comparison pages, and AI-generated drafts. For example, a billing SaaS should not begin with “write 50 finance keywords.” It should begin with verified product facts, the financial workflows buyers struggle with, the alternatives they compare, and the evidence required to support a claim. Keywords become demand clues—not a substitute for customer understanding. ## A better success statement Write the goal as a chain: “Become eligible for discovery around usage-based billing migrations, earn qualified evaluation visits, and increase completed sandbox projects.” That statement gives technical, editorial, and product teams a shared outcome. #### Practical checklist - Write one discovery chain for your highest-value buyer problem, from question to product action. - List five product claims and name the internal or public evidence that supports each one. - Choose one primary business outcome and two leading discovery signals for this course. #### Sources - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [Publishers and developers FAQ](https://help.openai.com/en/articles/12627856-publishers-and-developers-faq) — OpenAI Help Center; reviewed 2026-09-03 #### Related Blogged resources - [Knowledge Engine](https://blogged.dev/product/knowledge): Keep product and market facts governed before they reach content. - [Content Strategy](https://blogged.dev/product/content-strategy): Turn approved strategy into content directions and topics. - [Competitor Blog Watch](https://blogged.dev/product/competitor-watch): Use reviewed market signals instead of copying a competitor calendar. - [Editor](https://blogged.dev/product/editor): Create, verify, optimize, and convert from one editing workflow. - [Assets](https://blogged.dev/product/assets): Govern the visuals that support your product story. - [Autopilot](https://blogged.dev/product/autopilot): Scale a controlled research-to-publishing workflow. - [Blog Site](https://blogged.dev/product/blog-site): Publish on a fast, branded reader experience. - [Insights](https://blogged.dev/product/insights): Connect visibility signals with useful reader and conversion evidence. ### Lesson 2: Translate visibility into business goals URL: https://blogged.dev/courses/saas-seo-ai-visibility/visibility-business-goals Outcome: You will leave with a measurement ladder and a baseline that avoids false attribution. ## Measure a ladder, not one magic number Visibility is a sequence of observable states. Start with **eligibility**: can important pages be crawled, indexed, rendered, and understood? Then measure **exposure** such as impressions, citations, or appearances. Next comes **engagement**: qualified visits, useful reading, searches, CTA views, and clicks. Finally measure **outcomes** such as signups, activated workspaces, demos, pipeline, and retained revenue. Do not collapse the ladder into “AI traffic” or “organic conversions.” A cited page can shape a decision without a click; a referral can click without creating value; a signup can have several prior touchpoints. Report what the evidence supports and label assumptions. ## Define a baseline Choose a fixed baseline window before major changes. Record: - indexable and indexed priority pages; - non-branded search impressions, clicks, and representative query groups; - referral sessions from known search and AI interfaces; - assisted and last-touch conversion signals where your analytics supports them; - conversion rates only when denominators and consent coverage are known; - content freshness, broken journeys, and pages with no meaningful internal links. Segment by page type and intent. A product page, free tool, integration guide, and educational article play different roles. Comparing all pages by raw traffic rewards broad informational content even when a narrower page drives more qualified evaluation. ## Use claim-safe language Say “associated with,” “observed after,” or “last non-direct referrer” when causality is not established. Keep unknown traffic as unknown. Preserve campaign parameters across the journey, but do not pretend they reconstruct a person across devices, privacy boundaries, or untracked sessions. AI reporting is evolving. Bing Webmaster Tools introduced AI Performance reporting, and Google Search Console provides a generative AI performance report. Use first-party reports when available, but retain your own landing-page, referral, and conversion evidence because vendor definitions and coverage differ. ## Set a decision cadence Every metric needs a decision. Weekly: fix crawl failures and review important movements. Monthly: inspect query-page fit, citations, engagement, and conversion paths. Quarterly: change the portfolio and strategy. A dashboard without thresholds, owners, and actions is decoration. #### Practical checklist - Create a four-level ladder: eligibility, exposure, engagement, and outcome. - For every metric, write its source, known blind spots, owner, and decision threshold. - Save a dated baseline before publishing or technical changes begin. #### Sources - [Introducing AI Performance in Bing Webmaster Tools](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview) — Bing Webmaster Blog; reviewed 2026-09-03 - [Generative AI search performance report](https://support.google.com/webmasters/answer/16984139) — Google Search Console Help; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Search visibility](https://blogged.dev/product/insights/search-visibility): Inspect search queries and page-level visibility without treating impressions as revenue. - [Indexing coverage](https://blogged.dev/product/insights/indexing-coverage): Find published pages that are not represented in Search Console coverage. - [Content freshness](https://blogged.dev/product/insights/content-freshness): See which published content is becoming stale. - [CTA performance](https://blogged.dev/product/insights/cta-performance): Measure eligible CTA views and clicks with disclosed denominators. - [Lead attribution](https://blogged.dev/product/insights/lead-attribution): Inspect captured acquisition context without claiming causal identity stitching. - [Audience signals](https://blogged.dev/product/insights/audience-signals): Use reader, search, and feedback signals to guide the next iteration. ## Module 2: Become technically discoverable Give crawlers, search engines, AI systems, and people a reliable site to use. ### Lesson 3: Crawl, render, index, and serve reliably URL: https://blogged.dev/courses/saas-seo-ai-visibility/crawl-render-index Outcome: You will diagnose technical discovery in the right order instead of treating indexing as one switch. ## Four different gates **Crawling** is fetching a URL. **Rendering** is producing usable content from its HTML and required resources. **Indexing** is a system deciding to store and make that page eligible. **Serving** is selecting it for a particular request. Passing one gate does not guarantee the next. Start with the URL users should reach. Confirm a successful response, useful server-rendered HTML, one stable canonical, indexability, and links that a crawler can follow. Test without relying only on a browser's final visual state: a beautiful client-rendered shell can send thin initial HTML or fail when scripts are unavailable. ## Audit in dependency order 1. Resolve DNS and TLS reliably. 2. Return the intended status code without redirect loops. 3. Serve the main title, headings, copy, and links in meaningful HTML. 4. Check robots.txt access and page-level robots directives separately. 5. Confirm canonical and language signals match the intended URL. 6. Make the page reachable through crawlable internal links. 7. Inspect indexing tools and logs after the foundations are correct. A robots.txt disallow controls crawling; it is not a reliable way to remove an already known URL from search. A noindex directive must be fetched to be seen. Authentication, accidental 404s, soft 404s, server errors, infinite parameters, and duplicate routes each need different remedies. ## SaaS failure patterns Marketing migrations commonly leave chains from old slugs, canonical tags pointing at staging, orphaned feature pages, or JavaScript-only copy. Documentation and app routes can also leak into the public index when host or robots rules are too broad. Keep app/API paths private while preserving access to genuinely public product, tool, course, and blog pages. Use a bounded audit rather than assuming a crawler saw everything. Record tested URLs, exclusions, timeouts, and coverage limits. A “clean” audit over 50 pages is not proof that a 5,000-page site is clean. #### Practical checklist - Test one priority page from DNS through rendered HTML, directives, canonical, and internal discovery. - Separate every finding into crawl, render, index, or serve so the fix targets the right gate. - Document audit coverage and any untested route groups. #### Sources - [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) — Google Search Central; reviewed 2026-09-03 - [Introduction to robots.txt](https://developers.google.com/search/docs/crawling-indexing/robots/intro) — Google Search Central; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [SaaS robots.txt Generator](https://blogged.dev/free-tools/saas-robots-txt-generator): Audit crawler access and generate a reviewable policy. - [SaaS sitemap.xml Generator](https://blogged.dev/free-tools/saas-sitemap-xml-generator): Build a validated sitemap from observed canonical URLs. - [SaaS Blog SEO & AI Visibility Audit](https://blogged.dev/free-tools/saas-blog-seo-audit): Run a bounded technical, content, link, schema, and AI-crawler audit. - [Blog publishing](https://blogged.dev/product/blog-site/publishing): See Blogged's public publishing and discovery outputs. ### Lesson 4: Design canonicals, sitemaps, and redirects URL: https://blogged.dev/courses/saas-seo-ai-visibility/canonicals-sitemaps-redirects Outcome: You will produce a URL policy and migration checklist for your SaaS site. ## Give each useful page one durable address URL consistency compounds. Choose lowercase, readable slugs; define trailing-slash and host rules; remove unnecessary tracking parameters from canonical destinations; and keep public URLs stable when copy or design changes. A canonical is a **hint** about the preferred representative among duplicates. Reinforce it with redirects, internal links, sitemap entries, and consistent metadata. Do not canonicalize unrelated pages to a popular page, and do not expect a canonical to replace an information architecture. ## Build a truthful sitemap Include canonical, indexable, successful URLs you actually want discovered. Exclude redirects, errors, noindex pages, duplicate parameters, private app routes, and drafts. Use a meaningful last-modified timestamp only when the primary content changed—not every deployment or request. Split large sitemaps and expose the index in robots.txt. Sitemaps aid discovery; they do not guarantee indexing. If a page is absent from navigation and weak in value, a sitemap entry does not repair those problems. ## Redirect migrations as a mapping problem Before a migration, export old URLs and map each to the closest useful successor. Use a permanent server-side redirect, avoid chains, update internal links and canonicals to the destination, and preserve high-value query behavior where appropriate. Return 404 or 410 when there is no replacement instead of sending every retired URL to the homepage. After launch, monitor old URLs, redirect errors, canonical selection, sitemap processing, and landing-page performance. Keep redirects long enough for users, external links, and crawlers to adopt the new location. ## Keep generated files reviewable Generated robots.txt, sitemap.xml, and llms.txt outputs should state what was observed and what was excluded. Validate syntax and URLs. A generated file is a proposal to review, not authority to overwrite production policy blindly. #### Practical checklist - Write your canonical host, protocol, trailing-slash, parameter, and casing policy. - Compare your sitemap against canonical, indexable 200-status pages and list mismatches. - Create an old-to-new redirect map before changing any high-value URL. #### Sources - [How to specify a canonical URL](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) — Google Search Central; reviewed 2026-09-03 - [Build and submit a sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) — Google Search Central; reviewed 2026-09-03 - [Introduction to robots.txt](https://developers.google.com/search/docs/crawling-indexing/robots/intro) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [SaaS sitemap.xml Generator](https://blogged.dev/free-tools/saas-sitemap-xml-generator): Generate validated XML from observed canonical pages. - [SaaS robots.txt Generator](https://blogged.dev/free-tools/saas-robots-txt-generator): Review crawler policy alongside sitemap discovery. - [SaaS llms.txt Generator](https://blogged.dev/free-tools/saas-llms-txt-generator): Create a grounded, reviewable machine-readable site guide. - [Blog publishing](https://blogged.dev/product/blog-site/publishing): Review the canonical, sitemap, robots, RSS, and metadata publishing layer. ### Lesson 5: Build site architecture and internal links URL: https://blogged.dev/courses/saas-seo-ai-visibility/site-architecture-internal-links Outcome: You will turn a flat content inventory into a buyer-centered architecture and link plan. ## Architecture explains what belongs together A useful SaaS architecture starts with buyer tasks and product concepts, not an arbitrary depth rule. Group durable product pages, use-case pages, integrations, comparisons, tools, documentation, and educational content around clear parent concepts. Every important page should have a reason to exist and a sensible path from navigation or contextual links. Internal links do three jobs: they let people continue a task, expose URLs for crawling, and communicate relationships through surrounding language and anchor text. Use normal anchor elements with real destinations. Prefer descriptive wording such as “usage-based billing migration checklist” over “click here.” ## Link by reader need From an educational article, link to definitions, prerequisites, evidence, related decisions, and the relevant product capability. From a feature page, link to proof, setup guidance, alternatives, and the next product action. Avoid adding a block of unrelated keyword links simply to move authority. Create a rule for every new article: - link to the most relevant durable product or solution page; - link to two or more genuinely useful supporting resources when they exist; - receive at least one contextual link from an existing indexed page; - avoid duplicate or misleading anchors; - repair links when destinations move. ## Find structural gaps Export internal links or run a bounded crawl. Flag orphan pages, important pages with very few inbound links, broken destinations, redirecting links, excessive repeated navigation, and clusters that never connect to a commercial path. Review manually: link counts alone cannot tell whether a link is useful. For a project-management SaaS, an article about sprint retrospectives can connect to a retrospective template, agile workflow feature, reporting capability, and a guide to action items. That path helps the reader move from concept to execution and gives systems a coherent relationship to interpret. #### Practical checklist - Draw one topic cluster with a durable parent, supporting resources, and a commercial next step. - Identify five orphaned or weakly linked priority pages and choose contextual source pages. - Write descriptive anchor text that remains accurate outside the surrounding sentence. #### Sources - [Links best practices for Google](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) — Google Search Central; reviewed 2026-09-03 - [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) — Google Search Central; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Editor internal links](https://blogged.dev/product/editor/internal-links): Review and control relevant internal-link suggestions while editing. - [SaaS Internal Link Tool](https://blogged.dev/free-tools/saas-internal-link-tool): Generate a cited, bounded internal-link plan for a public site. - [Blog homepage and navigation](https://blogged.dev/product/blog-site/homepage-navigation): Organize categories, featured content, search, and reader paths. ### Lesson 6: Make the experience fast, mobile, and accessible URL: https://blogged.dev/courses/saas-seo-ai-visibility/mobile-performance-accessibility Outcome: You will define a practical quality budget across mobile performance and accessibility. ## Optimize the experience people actually receive Measure representative production pages on realistic mobile devices and networks. Lab tests explain repeatable bottlenecks; field data reflects real visits. Use both. Core Web Vitals focus on loading, responsiveness, and visual stability, but passing thresholds does not make confusing copy or an inaccessible interface good. Start with the critical path: server response, HTML, fonts, hero media, scripts, consent tooling, and third parties. Compress and size images, reserve dimensions to prevent layout shifts, avoid blocking font behavior, keep JavaScript budgets explicit, and load non-critical embeds after the main content. ## Accessibility improves the same journey Use semantic headings in order, visible focus, keyboard-operable controls, descriptive labels, sufficient contrast, useful alt text, captions where needed, and touch targets that work without precision. Error messages should explain the problem and recovery. Respect reduced-motion preferences. Do not put essential meaning only in color or an image. Accessibility conformance requires deliberate testing against WCAG—not a plugin score. Combine automated checks with keyboard testing, screen-reader spot checks, zoom, reflow, and contrast review. Include dialogs, menus, consent controls, forms, tables, code blocks, and mobile navigation. ## Create a regression budget Choose representative templates: homepage, product page, article, category, tool, and signup handoff. Set budgets for image weight, blocking scripts, layout stability, and interaction latency. Test at pull-request time where practical and sample field metrics after release. For a content-heavy SaaS blog, a fast first article is not enough. Related reading, CTA cards, tables of contents, newsletter forms, and analytics must stay usable at every breakpoint and with assistive technology. #### Practical checklist - Test one representative page at 320px, 768px, and a wide desktop without horizontal scrolling. - Complete the primary journey using only a keyboard and record every blocked or unclear control. - Set a performance and accessibility regression checklist for each shared template. #### Sources - [Web Vitals](https://web.dev/articles/vitals) — web.dev; reviewed 2026-09-03 - [Web Content Accessibility Guidelines 2.2](https://www.w3.org/TR/WCAG22/) — W3C; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Reader experience](https://blogged.dev/product/blog-site/reader-experience): See responsive reading, search, TOC, taxonomy, and related content behavior. - [Tracking and consent](https://blogged.dev/product/blog-site/tracking-consent): Keep measurement and consent visible without compromising the reader journey. - [Blog themes](https://blogged.dev/product/blog-site/themes): Choose presentation within a governed responsive theme system. - [Brand design](https://blogged.dev/product/blog-site/brand-design): Apply readable typography, color, and brand assets across the blog. ### Lesson 7: Use metadata, media, and structured data honestly URL: https://blogged.dev/courses/saas-seo-ai-visibility/metadata-media-structured-data Outcome: You will create a metadata and schema checklist grounded in visible page content. ## Start with the visible page A descriptive title, clear main heading, useful introduction, stable canonical, and coherent body matter more than clever tags. Write unique title and description metadata that accurately previews the page. Search systems may choose other snippets; metadata is an input, not a guaranteed display. Social metadata improves link previews. Use a dedicated image with readable text, meaningful alt text, correct dimensions, and a stable absolute URL. For article media, provide dimensions, responsive sources, descriptive filenames where useful, and alt text that communicates the image's purpose rather than stuffing terms. ## Structured data must match reality JSON-LD can make explicit what a page represents: organization, software application, article, breadcrumb, or learning resource. Use supported properties, valid URLs, and visible claims. Validate syntax and eligibility, but remember that correct markup never guarantees a rich result. Do not mark hidden testimonials, invented ratings, fake FAQs, or content that is not present. Do not create several thin “courses” to qualify for a course list. Google retired Course Info documentation in its 2025 search-result simplification, and FAQ rich results have limited eligibility. Generic Schema.org semantics can still describe content accurately; treat that as machine-readable meaning, not a display promise. ## Make facts easy to verify Place author, publisher, dates, product names, definitions, and cited claims where readers can see them. Use consistent naming across metadata, headings, copy, structured data, and organization profiles. If a product limitation matters, state it on the page instead of hiding it in markup. Keep generated metadata in the same content lifecycle as the page. When the primary copy changes materially, review the title, description, social card, structured data, and modified timestamp together. #### Practical checklist - Review a priority page for alignment across title, H1, canonical, social preview, and visible promise. - Validate its structured data and remove every claim that is not supported by visible content. - Create a social-card and alt-text standard for every repeatable page type. #### Sources - [Understand how structured data works](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) — Google Search Central; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [Simplifying the search results page](https://developers.google.com/search/blog/2025/06/simplifying-search-results) — Google Search Central Blog; reviewed 2026-09-03 #### Related Blogged resources - [SEO & GEO editor controls](https://blogged.dev/product/editor/seo-geo): Review search and answer-engine readiness while editing. - [Sources and citations](https://blogged.dev/product/editor/sources-citations): Keep external evidence visible and reviewable. - [Visual references](https://blogged.dev/product/assets/visual-references): Use approved references without treating generated output as an exact reproduction. ## Module 3: Turn demand into the right pages Research customer language, map the market, and prioritize a useful page portfolio. ### Lesson 8: Research customer language and intent URL: https://blogged.dev/courses/saas-seo-ai-visibility/customer-language-research Outcome: You will build an evidence-backed problem and language inventory for one audience segment. ## Begin with decisions customers make Search queries are fragments of a larger job. Combine customer interviews, sales calls, support tickets, onboarding questions, community language, Search Console queries, site search, and competitor positioning. Preserve exact phrases, but also record the situation, role, urgency, current workaround, desired outcome, and evidence source. Group evidence by **problem and intent**, not just shared words. A query asking “what is revenue recognition” needs education. “Revenue recognition software for SaaS” signals solution evaluation. “Product A vs Product B” needs a fair comparison. “How to migrate from spreadsheets” needs a workflow and risk plan. Each deserves a different page and conversion path. ## Distinguish signal from demand One loud customer request is not a market. High keyword volume is not product fit. Competitor coverage is not a mandate. Score opportunities with several inputs: audience fit, problem frequency, commercial relevance, evidence strength, product credibility, existing coverage, differentiation, and production cost. Maintain a living product-context record so content does not overstate capabilities. Record unsupported, stale, conflicting, or rejected facts and prevent them from entering drafts until resolved. ## Build a research brief For each priority problem, write the audience, job, stage, primary question, supporting questions, current alternatives, proof needed, relevant capability, objections, and next useful action. Add representative phrases and source links. This brief becomes the contract for page selection, research, and editorial review. The result should help a writer make decisions—not just display a keyword list. #### Practical checklist - Collect ten verbatim customer phrases and attach each to a source and situation. - Separate informational, evaluative, and action-oriented intent for one problem. - Write a one-page research brief with the proof and product facts the page may use. #### Sources - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) — Google Search Central; reviewed 2026-09-03 - [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Content directions](https://blogged.dev/product/content-strategy/content-directions): Define approved audiences, narratives, and boundaries. - [Topics](https://blogged.dev/product/content-strategy/topics): Turn evidence-backed directions into reviewable topic briefs. - [Product context](https://blogged.dev/product/knowledge/product-context): Govern product facts before they reach generation. - [Find My SaaS Competitors](https://blogged.dev/free-tools/saas-competitor-finder): Gather cited direct and indirect alternatives as one research input. ### Lesson 9: Map the competitive landscape without copying it URL: https://blogged.dev/courses/saas-seo-ai-visibility/competitive-landscape Outcome: You will create a dated market map and convert only relevant gaps into research questions. ## Buyers compare categories, workflows, and workarounds Your competitive set includes direct products, adjacent tools, services, spreadsheets, internal builds, and doing nothing. Map overlap by audience, job, capability, workflow, price model, and evidence—not by a single label. Review public sources with dates and links. Separate what a vendor claims from what you independently verified. A feature not observed on public pages is **not proven absent**. Product pages change, plans differ, and gated capabilities may be invisible. ## Turn monitoring into questions A competitor's new article, feature, or positioning change is a signal. Ask: - Does this connect to an approved audience and problem? - Do customers use the same language? - Can we contribute original product knowledge or evidence? - Do we already cover the intent on a stronger page? - Would responding clarify our category or merely imitate theirs? Only then create a topic or update. Keep a review gate between signal collection and production. ## Write fair comparison content State the scope and date. Link primary sources. Compare meaningful criteria for the target buyer. Explain where each option fits, including cases where your product is not the best choice. Avoid unsupported “best,” invented reviews, selective outdated pricing, and trademarks used deceptively. Competitive research should sharpen differentiation and reveal unanswered customer questions. If it only creates a bigger list of keywords, it has not done its job. #### Practical checklist - Map three direct, three indirect, and three non-software alternatives for one buyer job. - Attach dated primary evidence and an uncertainty label to every capability claim. - Review one competitor signal against audience fit, customer evidence, differentiation, and existing coverage. #### Sources - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies) — Google Search Central; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Monitoring signals](https://blogged.dev/product/competitor-watch/monitoring-signals): Collect reviewed, dated changes from approved competitors. - [Signal to Topic](https://blogged.dev/product/competitor-watch/signal-to-topic): Keep human review between a market signal and content production. - [Competitor intelligence](https://blogged.dev/product/knowledge/competitor-intelligence): Store source-bound competitor facts with verification state. - [SaaS Feature Gap Analyzer](https://blogged.dev/free-tools/saas-feature-gap-analyzer): Build a cited matrix that labels observed gaps honestly. ### Lesson 10: Design the SaaS page portfolio URL: https://blogged.dev/courses/saas-seo-ai-visibility/saas-page-portfolio Outcome: You will identify missing, overlapping, and misplaced pages across the customer journey. ## One page should own one durable promise Build a portfolio across homepage, product, feature, solution, use-case, integration, comparison, alternative, pricing, documentation, free-tool, glossary, research, template, and educational article pages. The right type follows the buyer's task. A feature page should explain the capability, workflow, evidence, limits, and next action. A use-case page organizes capabilities around a role or outcome. A comparison page helps a buyer evaluate options fairly. A free tool completes a bounded job. An article teaches a decision or method. Do not force every query into a blog post. ## Resolve overlap deliberately For each intent cluster, choose a primary page. Merge thin duplicates, differentiate genuinely distinct audiences or jobs, and link supporting pages to the owner. Cannibalization is not simply two pages sharing words; it is several pages competing to fulfill the same intent without a clear role. ## Connect information to product truth Educational content should naturally expose the relevant product capability when it helps the reader act. Product pages should link to deeper evidence and implementation guidance. Free tools can create immediate value and reveal the next workflow. Documentation supports adoption rather than carrying all acquisition messaging. Create a portfolio table with page type, audience, job, funnel role, primary promise, evidence, owner, freshness expectation, and conversion path. This becomes the bridge between strategy and a maintainable site. #### Practical checklist - Inventory priority URLs by page type, audience, intent, owner, and next action. - Choose the primary page for three overlapping intent clusters and decide merge, differentiate, or redirect. - Find one buyer task that deserves a tool, template, or product page rather than another article. #### Sources - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) — Google Search Central; reviewed 2026-09-03 - [Links best practices for Google](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Knowledge Engine](https://blogged.dev/product/knowledge): Ground every page type in governed product and market facts. - [Content Strategy](https://blogged.dev/product/content-strategy): Define the portfolio's approved audiences and narratives. - [Editor](https://blogged.dev/product/editor): Create and review the right content inside a governed workflow. - [Free SaaS tools](https://blogged.dev/free-tools/saas-blog-seo-audit): Use a bounded audit as a value-first discovery page. ### Lesson 11: Prioritize content responsibly URL: https://blogged.dev/courses/saas-seo-ai-visibility/prioritize-content-responsibly Outcome: You will create a transparent scoring and approval system for your content backlog. ## Prioritization is a resource decision Score ideas across audience fit, problem importance, evidence strength, product relevance, differentiation, intent value, current coverage, confidence, effort, and freshness burden. Weight the model to your stage and write down why. A score should support judgment, not disguise it. Add gates before production: the audience and direction are approved; required product facts are verified; the page type is correct; no existing page already satisfies the intent; the team can provide useful evidence; and an owner accepts the maintenance obligation. ## Avoid scaled-content traps Automation lowers production cost but not the standard for usefulness. Google's spam policies address scaled content abuse when many pages are produced primarily to manipulate rankings rather than help users. Programmatic pages need unique, reliable data and a real user task—not token substitutions across thousands of near-duplicates. Use automation to gather evidence, structure briefs, check consistency, and move approved work through a controlled process. Keep human review or explicit governed rules at high-risk decisions: strategy, claims, citations, legal/commercial statements, publication, and large portfolio changes. ## Manage supply and capacity Set backlog and publication limits. Separate ideas, approved Topics, drafts, scheduled posts, and published assets. Make failures and holds visible. A full queue should stop new intake or require reprioritization rather than silently growing. Revisit scores when product facts, customer evidence, market conditions, or existing coverage change. Archive ideas with a reason so they do not return without new evidence. #### Practical checklist - Create a weighted scorecard and test it against five very different ideas. - Define the evidence and approval gates required before a Topic can become a draft. - Set explicit capacity limits for ideas, approved Topics, drafts, and weekly publishing. #### Sources - [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies) — Google Search Central; reviewed 2026-09-03 - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Modes and governance](https://blogged.dev/product/autopilot/modes-governance): Choose assisted or full automation within explicit publication gates. - [Planning and Topic supply](https://blogged.dev/product/autopilot/planning-topic-supply): Keep approved Topics and schedule capacity visible. - [Freshness governance](https://blogged.dev/product/knowledge/freshness-governance): Prevent stale, rejected, or conflicting facts from entering generation. ## Module 4: Build the SaaS blog growth machine Create a governed publishing system that compounds knowledge, links, and conversion paths. ### Lesson 12: Why a powerful SaaS blog is a growth machine URL: https://blogged.dev/courses/saas-seo-ai-visibility/saas-blog-growth-loop Outcome: You will design a blog loop that connects market learning to product growth instead of publishing in isolation. ## A blog is an operating system, not a feed A strong SaaS blog captures what your company knows about customer problems, makes that knowledge discoverable, helps buyers evaluate decisions, and returns behavioral evidence to the team. Every useful article can strengthen topic coverage, internal links, product education, sales enablement, onboarding, and future research. The loop is: governed knowledge → approved strategy → evidence-backed Topics → researched drafts → editorial and conversion review → reliable publication → discovery and reader signals → refresh, prune, or expand. Each turn improves the inputs for the next. ## Why the loop compounds Durable articles can earn links and recurring discovery. A coherent cluster makes related pages easier to navigate and interpret. Repeated questions expose product messaging gaps. Search and on-site behavior reveal language customers use. Refresh work protects earlier investment. Relevant calls to action turn education into a next step without breaking trust. This compounding only happens when quality and maintenance are systematic. A stream of disconnected posts creates editorial debt, stale claims, orphan pages, and noisy measurement. ## Give the blog product-grade infrastructure Treat the blog like a product surface: branded domain, server-rendered pages, stable metadata, canonical URLs, sitemap, robots guidance, RSS, responsive templates, accessible navigation, categories, tags, search, table of contents, related reading, conversion components, consent, and analytics. Preview before publication and preserve revision history. ## Connect the loop to the company Product and support teams should contribute verified changes and customer questions. Marketing owns strategy and quality. Subject-matter experts review risky claims. Growth owns measurement. One named editor owns the final standard even when automation performs much of the mechanical work. The goal is not “publish more.” It is “turn company knowledge into useful, discoverable assets and learn from what happens next.” #### Practical checklist - Draw your current blog loop and mark every missing owner, gate, or feedback path. - Choose one existing article and list how it supports discovery, evaluation, product education, and conversion. - Define the minimum infrastructure and editorial standard every published article must meet. #### Sources - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [Links best practices for Google](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Autopilot](https://blogged.dev/product/autopilot): Move governed Topics through assisted or full publishing workflows. - [Blog Site](https://blogged.dev/product/blog-site): Serve the public reader, discovery, navigation, consent, and conversion layer. - [Insights](https://blogged.dev/product/insights): Feed search, reader, CTA, lead, and freshness evidence back into decisions. ### Lesson 13: Build topic systems, not keyword piles URL: https://blogged.dev/courses/saas-seo-ai-visibility/topic-systems Outcome: You will design a topic cluster and supply process that avoids duplication and backlog drift. ## Strategy constrains the topic universe Start with approved content directions: audience, customer problems, product narrative, boundaries, proof, and intended outcomes. A Topic is a specific, reviewable brief inside one direction—not a keyword handed directly to a writer. Balance the portfolio across foundational education, problem-solving workflows, evaluation, alternatives, implementation, original research, product-led teaching, and refresh work. Map each Topic to an existing parent or intended cluster and a meaningful next action. ## Define the Topic contract Include working title, audience, intent, primary question, supporting questions, page type, angle, evidence requirements, relevant product facts, internal-link targets, risks, and acceptance criteria. Record why the Topic exists and what existing page it must not duplicate. ## Maintain healthy supply Track proposed, approved, drafting, scheduled, published, held, and archived states. Refill only within approved directions and capacity. Deduplicate semantically, not just by title. A weekly monitor may discover market signals, but it should not silently publish or overwhelm the queue. Review cluster health monthly: missing intent, weak product connections, orphan pages, declining assets, and overproduction around easy terms. Sometimes the best next Topic is an update, consolidation, tool, or product-page improvement—not a new article. The system should make “why are we writing this?” answerable before research starts. #### Practical checklist - Define one approved content direction with audience, narrative, boundaries, and proof. - Create five complementary Topic briefs across different intent stages. - Set deduplication, capacity, refill, hold, and archive rules for the Topic queue. #### Sources - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies) — Google Search Central; reviewed 2026-09-03 - [Links best practices for Google](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [Content Strategy](https://blogged.dev/product/content-strategy): Create an approved strategy blueprint before Topic generation. - [Content directions](https://blogged.dev/product/content-strategy/content-directions): Constrain audiences, narratives, and boundaries. - [Topics](https://blogged.dev/product/content-strategy/topics): Review concrete briefs before they enter production. - [Product context](https://blogged.dev/product/knowledge/product-context): Attach eligible product facts to each brief. ### Lesson 14: Research and write evidence-led content URL: https://blogged.dev/courses/saas-seo-ai-visibility/evidence-led-content Outcome: You will create an evidence table and editorial standard for claims before drafting. ## Claims need an evidence plan Before drafting, list the claims the article must make. Classify each as product fact, external fact, analysis, opinion, example, or hypothesis. Assign the best available evidence and freshness requirement. Prefer primary sources for product specifications, standards, research, laws, and platform behavior. Use credible secondary sources for synthesis and context. Link directly to the supporting page, preserve publication or review dates, and avoid citing a source that merely repeats the claim without evidence. ## Add information gain honestly Useful originality can come from product expertise, a worked example, a transparent framework, a customer-derived pattern with privacy preserved, a benchmark with disclosed methods, or a clear synthesis across sources. It does not require inventing certainty. Separate observed fact from inference. State sample limits, dates, assumptions, and conflicts. Do not turn a controlled academic benchmark into a universal traffic promise. The original GEO study reported gains in its controlled benchmark; later survey work highlights unresolved measurement and causal questions across real platforms. ## Keep product truth governed Use only verified, current facts eligible for publication. Conflicting or stale facts should block risky claims, not be averaged into a confident sentence. Link readers to the product page or documentation that supports the claim and state important limitations. ## Review beyond grammar The final review checks intent satisfaction, claim support, source quality, product accuracy, originality, structure, accessibility, internal links, conversion fit, and metadata. AI assistance can accelerate research organization and prose, but accountability remains with the publisher. #### Practical checklist - Build a claim-evidence table for one planned article before writing its outline. - Replace one vague authority signal with a direct primary source and reviewed date. - Label fact, inference, example, and uncertainty explicitly in a draft section. #### Sources - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [GEO: Generative Engine Optimization](https://arxiv.org/abs/2311.09735) — arXiv; reviewed 2026-09-03 - [Generative Engine Optimization: A Critical Survey](https://arxiv.org/abs/2607.14035) — arXiv; reviewed 2026-09-03 #### Related Blogged resources - [Sources and citations](https://blogged.dev/product/editor/sources-citations): Review source coverage and reader-facing citations inside the Editor. - [Sources and verification](https://blogged.dev/product/knowledge/sources-verification): Keep facts source-bound and verification-gated. - [Competitor intelligence](https://blogged.dev/product/knowledge/competitor-intelligence): Retain dated market evidence without presenting unobserved gaps as facts. ### Lesson 15: Draft, illustrate, link, and convert URL: https://blogged.dev/courses/saas-seo-ai-visibility/draft-illustrate-link-convert Outcome: You will apply a complete pre-publication workflow to one SaaS article. ## Draft for the reader's decision Open with the problem and promised outcome. Use descriptive headings, short paragraphs, concrete examples, and definitions where ambiguity matters. Put the answer before background. Keep the narrative focused enough that every section helps the reader complete the intended job. ## Use visuals to explain Add an image, diagram, table, or annotated screenshot only when it makes a relationship, process, comparison, or interface easier to understand. Verify rights and source. Approved product assets should remain traceable to the Project and article. If AI generates an image from a reference, treat the reference as guidance—not a promise of exact reproduction. Provide useful alt text and preserve dimensions. ## Connect the article Review suggested internal links for relevance and accurate anchors. Link to prerequisite concepts, supporting evidence, adjacent workflows, and the durable product capability. Add inbound links from existing pages after publication. Avoid an arbitrary link quota. ## Design the next useful action The CTA should resonate with the lesson the reader just completed. A technical audit article can offer an audit tool; a strategy article can invite the reader to build a content direction; an implementation guide can invite signup or documentation. State what happens next. Do not disguise an ad as the answer. ## Preview the real destination Review the article inside its actual theme and route at mobile and desktop sizes. Check title, table of contents, anchors, code and tables, media, links, CTA, form, consent, related reading, metadata, canonical, and structured data. Exporting or previewing should never publish by surprise. Save a revision before important changes and make publication state explicit. #### Practical checklist - Rewrite one introduction so the problem, answer, and promised outcome appear immediately. - Add one functional visual with a clear purpose, rights record, dimensions, and alt text. - Review every internal link and CTA for reader relevance, then preview the real mobile page. #### Sources - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [Links best practices for Google](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) — Google Search Central; reviewed 2026-09-03 - [Web Content Accessibility Guidelines 2.2](https://www.w3.org/TR/WCAG22/) — W3C; reviewed 2026-09-03 #### Related Blogged resources - [AI images](https://blogged.dev/product/editor/ai-images): Generate and review article visuals in context. - [Conversion](https://blogged.dev/product/editor/conversion): Add CTA and lead components that match the article. - [Create posts](https://blogged.dev/product/editor/create-posts): Start from an approved Topic, custom brief, or Markdown. - [Preview and export](https://blogged.dev/product/editor/preview-export): Inspect the real blog privately or export without publishing. - [Website discovery](https://blogged.dev/product/assets/website-discovery): Discover candidate visuals from the approved site. - [Library governance](https://blogged.dev/product/assets/library-governance): Approve, reject, label, and retain asset history. - [Article placement](https://blogged.dev/product/assets/article-placement): Place approved site-scoped visuals into the article. - [Visual references](https://blogged.dev/product/assets/visual-references): Guide generation with approved references and explicit limits. ### Lesson 16: The Blogged blog-site blueprint URL: https://blogged.dev/courses/saas-seo-ai-visibility/blogged-blog-site-blueprint Outcome: You will audit your current blog against a production-grade SaaS publishing blueprint. ## Discovery is part of the publishing contract Blogged serves public articles with server-rendered titles, descriptions, canonicals, social metadata, and JSON-LD. The blog exposes sitemap, robots, and RSS discovery files and uses content-modified timestamps rather than pretending every deployment changed every article. Draft and preview states remain separate from public publication. ## The reader experience is a system Customer blogs include responsive layouts, deterministic table-of-contents anchors on mobile and desktop, category and tag navigation, on-site search, and up to three related articles selected from shared taxonomy. Calls to action and newsletter forms can continue the journey without replacing the article's answer. ## Brand and domain choices remain explicit Themes control presentation, not content ownership or substance. Brand controls cover typography, color, and identity assets. A branded custom subdomain is the recommended public destination; hosted subdomains and reverse-proxy configurations support other deployment needs. Tenant-specific icons and social previews preserve identity across tabs and shares. ## Measurement respects consent and evidence Tracking and consent controls are part of the public reader experience. Search, reader, CTA, lead, channel, and campaign reports describe observed signals and known denominators. They do not promise person-level identity stitching or prove that one article caused a sale. ## Governance continues after launch Publishing connects approved strategy, product knowledge, Topic review, source checks, internal links, media governance, private preview, and revision history. Search and freshness signals feed the next decision. Important limits stay visible: Blogged does not guarantee rankings, does not claim universal AI-mention tracking, and does not turn attribution evidence into causality. Use this blueprint as a checklist whether you run Blogged or your own stack. The value is the complete contract: technically discoverable, readable, branded, connected, measurable, and governed. #### Practical checklist - Audit your blog against discovery, reader, brand/domain, measurement, and governance layers. - Test TOC anchors, search, categories, tags, related reading, CTA, and consent on mobile and desktop. - Write down every metric limitation and product promise your public reporting must preserve. #### Sources - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [Links best practices for Google](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) — Google Search Central; reviewed 2026-09-03 - [Web Content Accessibility Guidelines 2.2](https://www.w3.org/TR/WCAG22/) — W3C; reviewed 2026-09-03 #### Related Blogged resources - [Blog Site](https://blogged.dev/product/blog-site): Review the complete public publishing surface. - [Themes](https://blogged.dev/product/blog-site/themes): Choose a governed presentation system. - [Brand design](https://blogged.dev/product/blog-site/brand-design): Apply typography, color, identity assets, and icons. - [Homepage and navigation](https://blogged.dev/product/blog-site/homepage-navigation): Organize featured content, categories, search, and discovery. - [Publishing](https://blogged.dev/product/blog-site/publishing): Use stable metadata, discovery files, previews, and domain options. - [Reader experience](https://blogged.dev/product/blog-site/reader-experience): Serve TOC, taxonomy, search, related reading, and responsive layouts. - [Tracking and consent](https://blogged.dev/product/blog-site/tracking-consent): Capture disclosed reader and conversion signals within consent controls. ## Module 5: Earn AI visibility Make trustworthy information easy to retrieve and cite while keeping crawler control explicit. ### Lesson 17: Design for retrieval, citation, and verification URL: https://blogged.dev/courses/saas-seo-ai-visibility/retrieval-citation-evidence Outcome: You will restructure one page around answerable questions and verifiable evidence. ## AI visibility still begins with useful web pages Google states that established SEO fundamentals remain relevant to AI features and that no special AI-only markup or text-file requirement is needed for eligibility. Build crawlable, indexable pages that satisfy users first. Retrieval benefits from clear information structure. Use a descriptive title and headings, answer the main question directly, define ambiguous entities, keep related evidence near the claim, and break complex processes into meaningful steps. Tables work for genuine comparisons; prose works for nuance. Do not mechanically “chunk” every sentence for machines at the expense of readers. ## Make verification cheap Attach dates, authorship, methods, primary sources, product versions, and scope to claims that can change. Publish stable URLs for durable facts. Link to evidence and preserve visible limitations. Keep organization and product naming consistent across your site and trusted external profiles. ## Earn references beyond your own domain Useful tools, original data, transparent methods, expert explanations, documentation, and fair comparisons can earn links and mentions. Partnerships, public profiles, review ecosystems, communities, and press may strengthen recognition when they are authentic. Manufactured mentions, paid link schemes, and reputation abuse create risk rather than durable authority. ## Measure with restraint Track citations and referral visits where first-party tools expose them, plus the landing pages and outcomes that follow. A citation count is an exposure signal, not a ranking factor you control and not revenue. Compare platforms and periods cautiously because coverage and answer behavior change. #### Practical checklist - Rewrite one key section so the answer, entity, scope, date, and evidence are immediately clear. - List five durable facts that deserve stable, directly linkable pages. - Separate citation exposure, referral engagement, and product outcomes in your reporting. #### Sources - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [Publishers and developers FAQ](https://help.openai.com/en/articles/12627856-publishers-and-developers-faq) — OpenAI Help Center; reviewed 2026-09-03 - [Generative Engine Optimization: A Critical Survey](https://arxiv.org/abs/2607.14035) — arXiv; reviewed 2026-09-03 #### Related Blogged resources - [SEO & GEO controls](https://blogged.dev/product/editor/seo-geo): Review answer readiness without inventing AI-specific ranking guarantees. - [Sources and citations](https://blogged.dev/product/editor/sources-citations): Keep evidence reader-facing and attached to the claim. - [Search visibility](https://blogged.dev/product/insights/search-visibility): Inspect first-party search evidence by query and page. - [Indexing coverage](https://blogged.dev/product/insights/indexing-coverage): Verify that published assets enter observable search coverage. ### Lesson 18: Control AI crawlers deliberately URL: https://blogged.dev/courses/saas-seo-ai-visibility/ai-crawler-controls Outcome: You will create a reviewed crawler policy based on your actual publishing goals. ## A crawler name is not a complete policy AI providers may use different user agents for search discovery, model training, and user-requested fetching. OpenAI distinguishes OAI-SearchBot from GPTBot. Anthropic documents ClaudeBot, Claude-SearchBot, and Claude-User. Perplexity documents PerplexityBot and Perplexity-User. Read each provider's current documentation before writing rules because names and behavior can change. Decide separately whether you want public pages eligible for search answers, available for user-requested retrieval, or available for model training. Consider legal, licensing, privacy, security, and commercial requirements with the appropriate owner. ## Robots.txt has boundaries Robots.txt is public guidance for cooperative crawlers. It does not authenticate a requester, protect confidential information, or guarantee deindexing. Keep private content behind authorization. Validate groups and paths, preserve existing search rules, declare sitemap locations, and avoid broad blocks caused by one misplaced slash. Page-level directives, HTTP headers, authentication, and provider controls solve different problems. Test representative public, private, asset, API, and application paths after every change. ## Treat llms.txt honestly An llms.txt file can provide a concise, machine-readable map for systems that choose to use it, but it is an emerging proposal rather than a universal ranking standard. Google explicitly says AI-feature eligibility does not require a new AI text file. Publish llms.txt only when it is accurate, grounded in public pages, maintained, and useful as documentation. Keep a dated policy record with owner, rationale, source documentation, intended access, and test evidence. Re-review it when providers or business goals change. #### Practical checklist - List current crawler groups by search, training, and user-requested purpose using primary documentation. - Write the desired policy for public marketing, blog, docs, app, API, and private routes before editing syntax. - Validate robots.txt and llms.txt against representative URLs and preserve a dated review record. #### Sources - [Publishers and developers FAQ](https://help.openai.com/en/articles/12627856-publishers-and-developers-faq) — OpenAI Help Center; reviewed 2026-09-03 - [Does Anthropic crawl data from the web, and how can site owners block the crawler?](https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler) — Anthropic Help Center; reviewed 2026-09-03 - [Perplexity crawlers](https://docs.perplexity.ai/docs/resources/perplexity-crawlers) — Perplexity Documentation; reviewed 2026-09-03 - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 #### Related Blogged resources - [SaaS robots.txt Generator](https://blogged.dev/free-tools/saas-robots-txt-generator): Audit and draft a crawler policy from verified user-agent documentation. - [SaaS llms.txt Generator](https://blogged.dev/free-tools/saas-llms-txt-generator): Generate a grounded file without claiming it is a ranking standard. - [Tracking and consent](https://blogged.dev/product/blog-site/tracking-consent): Keep public measurement controls distinct from crawler access policy. ### Lesson 19: Create citation-worthy content—and reject the myths URL: https://blogged.dev/courses/saas-seo-ai-visibility/citation-worthy-content-myths Outcome: You will choose one defensible citation asset and remove misleading AI claims from your playbook. ## Build assets worth referencing Strong candidates include original research with transparent methods, free tools that complete a real task, definitive product documentation, versioned benchmarks, public datasets, expert frameworks, calculators, templates, and unusually clear explanations of difficult decisions. Keep them current and easy to link directly. Citation-worthiness is not a formatting trick. It combines relevance, clarity, evidence, distinctiveness, accessibility, and trust. A concise answer can help retrieval, but it should sit inside a page that supplies method, context, exceptions, and next steps. ## Reject unsupported shortcuts There is no general requirement for special “AI schema,” an llms.txt file, machine-only wording, or a separate AI version of every page. Do not chase fake author biographies, keyword-stuffed answer blocks, paid mentions, synthetic consensus, or mass rewrites that remove expertise. Google says the same SEO fundamentals apply to its AI features and warns against scaled abuse and inauthentic value. Academic GEO experiments are useful research, not universal production guarantees. The original paper reported visibility improvements in a controlled benchmark. A later critical survey describes substantial open questions around measurement, platform variation, causal inference, and downstream business effects. Present both the result and its boundary. ## Build a defensible asset brief Define the user problem, why your company can answer it, data or expertise available, method, update cadence, review owner, target audiences, distribution plan, and product connection. Decide what would make the asset no longer reliable and how you will signal that. The best AI-visibility program looks remarkably like excellent publishing: create trustworthy things people want to use and reference, make them technically accessible, and measure without pretending certainty. #### Practical checklist - Choose one citation asset your company is uniquely qualified to maintain and write its method and update plan. - Audit your roadmap for AI-only tactics that lack primary evidence or user value. - Rewrite one performance claim to include its benchmark, scope, date, and uncertainty. #### Sources - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies) — Google Search Central; reviewed 2026-09-03 - [GEO: Generative Engine Optimization](https://arxiv.org/abs/2311.09735) — arXiv; reviewed 2026-09-03 - [Generative Engine Optimization: A Critical Survey](https://arxiv.org/abs/2607.14035) — arXiv; reviewed 2026-09-03 #### Related Blogged resources - [Sources and verification](https://blogged.dev/product/knowledge/sources-verification): Keep claims bound to eligible, reviewable evidence. - [Freshness governance](https://blogged.dev/product/knowledge/freshness-governance): Expire or resolve stale and conflicting facts before generation. - [Sources and citations](https://blogged.dev/product/editor/sources-citations): Show readers where factual claims come from. - [SaaS Feature Gap Analyzer](https://blogged.dev/free-tools/saas-feature-gap-analyzer): See a method-bound tool that reports observation limits. ## Module 6: Run the operating system Apply the course as a measured 90-day program with clear owners and review points. ### Lesson 20: Your 90-day SEO and AI visibility system URL: https://blogged.dev/courses/saas-seo-ai-visibility/ninety-day-seo-ai-system Outcome: You will leave with a prioritized 90-day plan, owners, gates, and a review cadence. ## Days 1–30: establish truth and eligibility Name owners. Save the baseline. Verify product and market facts. Inventory page types and important URLs. Fix critical crawl, render, indexability, canonical, redirect, sitemap, mobile, accessibility, and analytics failures. Define crawler policy and measurement limitations. Approve the first content directions and portfolio priorities. Ship a small number of high-confidence repairs and one useful cornerstone asset. Do not wait for a perfect audit, but do not scale production on a broken foundation. ## Days 31–60: build connected assets Create evidence-backed Topic briefs across the buyer journey. Refresh or consolidate overlapping pages before adding more. Produce articles, tools, product pages, or comparisons with visible sources, internal links, functional visuals, and contextual CTAs. Preview the real experience and preserve editorial approval. Build cluster connections in both directions. Distribute through channels where the audience already participates. Ask partners or experts for feedback when they genuinely improve the asset—never as a manufactured mention campaign. ## Days 61–90: learn and govern Review eligibility, exposure, engagement, and outcome signals by page type and intent. Investigate material changes rather than reacting to daily noise. Refresh weak evidence, repair journey gaps, expand assets that reveal useful demand, and archive ideas that no longer fit. Document what changed and what remains uncertain. Set the next quarterly portfolio around evidence, not a target article count. ## Weekly operating rhythm - Technical health and publication failures. - Search, AI, reader, and market signals requiring review. - Topic supply, drafts, schedule, and holds. - Product-fact freshness and source conflicts. - Conversion-path quality and meaningful outcomes. ## Your final safeguards No ranking or citation guarantees. No unsupported product claims. No scaled pages without unique value. No public draft leaks. No crawler-policy edits without review. No conversion rate without a denominator. No “AI revenue” claim without an attribution method. Keep these constraints visible as the system grows. #### Practical checklist - Assign an owner and due date to every day-30 foundation item. - Choose the first five assets by evidence, buyer value, product fit, and maintenance capacity. - Schedule weekly and monthly reviews with explicit decisions, not dashboard viewing. - Write your public and internal non-guarantee language for rankings, citations, attribution, and audit coverage. #### Sources - [AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) — Google Search Central; reviewed 2026-09-03 - [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) — Google Search Central; reviewed 2026-09-03 - [Spam policies for Google web search](https://developers.google.com/search/docs/essentials/spam-policies) — Google Search Central; reviewed 2026-09-03 - [Generative AI search performance report](https://support.google.com/webmasters/answer/16984139) — Google Search Console Help; reviewed 2026-09-03 - [Introducing AI Performance in Bing Webmaster Tools](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview) — Bing Webmaster Blog; reviewed 2026-09-03 #### Related Blogged resources - [Autopilot command center](https://blogged.dev/product/autopilot/command-center): Monitor scheduled work, holds, and activity from one operating surface. - [Content freshness](https://blogged.dev/product/insights/content-freshness): Bring aging published assets into the next review cycle. - [CTA performance](https://blogged.dev/product/insights/cta-performance): Review visible CTA exposure and clicks with denominator safeguards. - [Lead attribution](https://blogged.dev/product/insights/lead-attribution): Retain acquisition context without overstating causality. - [Audience signals](https://blogged.dev/product/insights/audience-signals): Use reader behavior and feedback as inputs to the next plan. - [SaaS Blog SEO & AI Visibility Audit](https://blogged.dev/free-tools/saas-blog-seo-audit): Create a bounded baseline across technical, content, link, schema, and crawler checks.