Salesforce Agentforce and SEO: What Changes for Organic Visibility

Traditionally, a buyer searches, lands on a page, reads and maybe contacts sales. With an agent on the site, the buyer lands and asks a question directly: “Does this integrate with SAP?” or “What is the lead time for 500 units?” The agent answers from knowledge articles and data, and may book a meeting or create a case.

Search still brings the buyer to the site in the first place. What changes is the depth of the visit. Many detailed questions that once required browsing several pages are now answered in conversation, so page views per visit may fall while conversion from engaged visits may rise.

The conversation itself is not indexed by search engines, so agent answers do not rank. The knowledge that feeds the agent can. If your Salesforce Knowledge articles, help centre pages and product documentation are published on crawlable URLs, the same content serves the agent and search engines.

The risk is building knowledge only inside the agent. If answers live in private instructions or unpublished articles, search engines and AI search tools never see them, and organic visibility for those questions drops to zero.

• Publish knowledge articles on public, crawlable URLs when the content is not confidential.
• Use clear headings and one question per article where possible.
• Keep one source of truth so the agent and the website give the same answer.
• Add FAQ and product schema where it accurately reflects page content.

Specific, factual content gains importance: integration lists, specifications, pricing rules, lead times, compatibility tables and troubleshooting steps. These are exactly the questions agents answer and AI search tools cite. Vague marketing pages help neither.

Content freshness also matters more. An agent that quotes an outdated policy creates a service problem immediately, and the same outdated page published on the web misleads search users. Assign owners and review dates to knowledge content.

Conversation data as keyword research

Agent conversations reveal the exact questions buyers ask, in their own words. Export common topics regularly and compare them with your content. Questions that the agent cannot answer, or answers often escalated to a person, point to missing pages that likely have search demand too.

Agent widgets load scripts on every page. Check that they do not slow Largest Contentful Paint or Interaction to Next Paint beyond Core Web Vitals thresholds; Google considers an LCP of 2.5 seconds or less as good. Load the widget after the main content where possible.

Also check Experience Cloud or other Salesforce-hosted help sites for indexation. Confirm that knowledge pages are not blocked by robots rules, that they have unique titles and descriptions, and that duplicate article versions do not compete with each other.

• Organic landing page traffic for knowledge and product pages, from Search Console.
• Agent engagement rate on organic visits, from your analytics and Agentforce reporting.
• Conversion rate of organic sessions with and without agent interaction.
• Unanswered or escalated agent questions, mapped to content gaps.
• Visibility in AI search answers for key product questions, tracked with a fixed prompt set.

No, but they change what landing pages need to do. A page still has to rank, earn the click and establish trust within seconds. The agent then picks up detailed questions that the page cannot cover without becoming unreadable. Pages can stay focused while the agent handles the long tail of specifics.

This makes page and agent design a joint task. If analytics show that visitors from a given landing page always ask the agent the same question, the answer probably belongs on the page itself. Treat agent transcripts as on-page feedback and update content accordingly.

Internal links still matter

Agents can link visitors to pages, but search engines still discover and value pages through internal links. Keep knowledge articles connected to the product and category pages they support, with descriptive anchor text. Orphaned help articles help neither the agent’s users nor organic rankings.

Measuring before launch

Record baseline organic traffic, engagement and conversion for knowledge pages before the agent goes live, so later changes can be compared fairly. Note the date the widget was installed in your analytics annotations, because traffic and engagement patterns often shift that week.