Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill experience-cloud-seo-settingsgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/experience-cloud-seo-settings)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/experience-cloud-seo-settings"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/experience-cloud-seo-settings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/experience-cloud-seo-settings"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/experience-cloud-seo-settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00093 | $0.02820 |
| Opus 5 | $0.00046 | $0.01410 |
| Sonnet 5 | $0.00019 | $0.00564 |
| Haiku 4.5 | $0.00009 | $0.00282 |
Grade A, and why
experience-cloud-seo-settings scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experience Cloud SEO Settings
This skill activates when a practitioner needs to configure search-engine visibility for an Experience Cloud site — covering per-page SEO properties in Experience Builder, automatic sitemap.xml generation, custom robots.txt implementation via Visualforce, and URL structure choices. It does not cover external SEO tooling or Salesforce CMS headless delivery.
Before Starting
Gather this context before working on anything in this domain:
- Org type: SEO features are only active on production orgs. Sandbox and scratch org sites will not generate a live sitemap or honor robots.txt for external crawlers. Confirm the target environment is production before diagnosing SEO issues.
- Site technology: LWR sites use clean URL paths without the
/sprefix. Aura (Community Builder) sites include/sin URLs. This affects URL structure decisions and sitemap paths. - Domain model: Determine whether the site uses a custom domain on a subdomain (
community.example.com) or on a subpath of a shared domain (example.com/community). Sites sharing a subpath share a single robots.txt file — this is the most common source of robots.txt confusion. - Guest profile access: Sitemap.xml automatically includes pages and objects that the site's guest user profile can read. Objects or pages the guest user cannot access will be silently excluded from the sitemap.
- Knowledge articles and topics: Knowledge articles are excluded from sitemap.xml unless they are assigned to a Data Category or a Topic. This is a common source of missing Knowledge pages in search engines.
Core Concepts
Per-Page SEO Properties in Experience Builder
Every page in an Experience Builder site has an SEO properties panel accessible from the page's gear icon (Page Settings > SEO). Available properties:
- Title — becomes the
<title>HTML element; also populates Open Graphog:title. - Meta Description — populates
<meta name="description">. Recommended 150–160 characters. If left blank, the platform may auto-generate one from page content. - No Index — when checked, adds
<meta name="robots" content="noindex">to the page. This signals search engines not to index the page but does not prevent crawling. A noindex page that is publicly accessible will still be crawled; only indexing is suppressed.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 204 lines · 93 tokens per session scan A 84627a5728fb
experience-cloud-seo-settings is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 93 tokens to every session and 2,820 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
startup-marketing-playbook
Marketing playbook for bootstrapped startups with zero budget. Covers organic-only channels including SEO, community building, social media, and word-of-mouth tactics that cost nothing but time. Follow @WeiYipei on X.
yandex-webmaster
Loaded automatically when the description matches the active task. Read only the section you need, then follow the link to the relevant reference file.
ecommerce-seo
Maximize organic search traffic with optimized product page meta tags, JSON-LD structured data for Google Shopping, and automated XML sitemaps.
community-engagement-strategy
Design the engagement model for an Experience Cloud community: reputation levels, ideation, and content contribution strategy. Triggers: 'community engagement strategy', 'gamification Experience Cloud', 'reputation levels setup', 'ideation community portal', 'member recognition program'. NOT for blocking, flagging or…
press-media-relations
Use when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the…
launch-monitor
Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"; runs the T-0 to T+30 window watch — pre-launch instrumentation verification (UTM/event checks, the upstream of RAMP P1), HN rank/points/comments polling with a comments-over-points flamewar…