Sight AI

View saved version →

---
name: check-ai-visibility
description: Report how often AI answers and AI search results mention or cite a site in Sight AI, broken down by assistant, how that is trending, and which content would help. Use when the user asks about AI visibility, AI search, brand mentions in AI answers, or AI citations.
---

Use this skill when the user asks how their brand shows up in AI answers. All of these tools read data; none needs confirmation.

## Pick the site

1. Call `list_sites` and settle on one site. Every other tool takes its `siteId`.

## Read the data

2. Call `get_ai_visibility_summary` with the window in `days` for the headline numbers: how many tracked prompts named the brand or cited the site, by platform.
3. Call `get_ai_visibility_trends` for the same window to show the direction over time.
4. Call `get_ai_visibility_mentions` for the breakdown by AI model and `get_ai_visibility_citations` for the pages AI assistants cite, with their stats.
5. Call `get_ai_visibility_competitors` to compare against the configured competitors.
6. For Google specifically, call `get_seo_ai_mode` for AI Mode results per tracked prompt: cited or not, the citation position, the cited URLs and citations lost since the previous check.
7. For what to write next, call `list_opportunities` with `source` set to `ai`: content opportunities built from prompts where the brand is absent.

## Presenting results

- Distinguish "mentioned" (the brand is named in the answer) from "cited" (the site is linked as a source). Report both with the window and the platform.
- Use the tools' percentages and counts as returned. If tracking started recently, say so instead of describing a trend.
- When a competitor is cited for prompts the site is not, point at the opportunity rows that cover those prompts.

## Do not

- Do not run AI checks yourself or ask other tools to query AI models; Sight AI tracks the prompts on a schedule and these tools report the results.
- Do not add or edit tracked prompts from here; that is done in the Sight AI app.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: compare-competitors
description: Compare a site with its SEO competitors in Sight AI: who they are, the keywords they rank for that the site does not, their top pages, share of voice and SERP features, and turn the gaps into tracked keywords. Use when the user asks who their competitors are, what competitors rank for, or how they compare in Google.
---

Use this skill when the user wants to understand or act on competitors. Reads need no confirmation; changing the competitor list, adding keywords and uncached domain lookups do.

## Pick the site

1. Call `list_sites` and settle on one site. Every other tool takes its `siteId`.

## Who the competitors are

2. Call `get_seo_competitors` for the current list (up to ten domains) and the side-by-side numbers from the latest snapshots: organic keywords and traffic, top 3 and top 10 counts, domain rank, backlinks, referring domains.
3. If the list is empty or the user wants suggestions, tell them it is a paid lookup, then call `suggest_seo_competitors`: domains that share the site's search results, with how many keywords they share.
4. To change the list, confirm the domains and call `add_seo_competitor` or `remove_seo_competitor` with the `domain`, or `set_seo_competitors` with the whole list to replace it. New domains get their keywords pulled in the background; say the comparison fills in over the next minutes.

## What they rank for

5. Call `get_competitor_keywords` with `view` "summary" for the headline numbers, per-competitor stats, article groups (keywords grouped by the competitor page that covers them) and brand plays such as "competitor alternatives" or "competitor pricing" articles.
6. For rows, call it with `view` "keywords" and filter: `kind` "missing" (the site does not rank), "behind" (ranks worse) or "ahead"; `competitorDomain` for one competitor; `minVolume` and `maxDifficulty` for the easy wins; `brand` "exclude" to drop branded searches.
7. Call `get_competitor_pages` for each competitor's top pages by estimated traffic, flagged when new since the previous refresh.
8. Call `get_seo_serp_features` to see who owns the AI Overview, featured snippet, People also ask and other features, and `get_seo_visibility` for the visibility index and share of voice over time.
9. For any domain not on the list, `explore_domain` gives the organic overview, top keywords, backlink summary and top pages. It is served from a seven-day cache when one exists; an uncached lookup is paid and capped per day, so check `get_seo_explore_recent` first and confirm before a fresh one.

## Act on the gaps

10. To track gap keywords, confirm the picks and call `add_competitor_keywords` with the rows' `opportunityIds` (up to 100). Use `dismiss_competitor_keyword` for a row the user rejects. To pull fresh competitor data, call `refresh_competitor_keywords` (queued; `force` ignores the 24-hour freshness window).

## Do not

- Do not call `suggest_seo_competitors`, `explore_domain` with `refresh`, or a competitor refresh without saying it spends the site's lookup budget.
- Do not change the competitor list without naming the domains and getting a yes.
- Do not rank competitors by anything other than the numbers the tools return.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: find-keywords-and-draft
description: Research high volume, low competition keywords for a site in Sight AI, save the best ones to a keyword list, and draft or generate an article for one of them. Use when the user asks for keyword ideas, content to write, or a new blog post.
---

Use this skill when the user wants keyword ideas or a new article. Keyword research spends the site's daily lookup budget and article generation spends the team's AI credits, so confirm before either.

## Pick the site and the seed

1. Call `list_sites` and settle on one site. Every other tool takes its `siteId`.
2. Turn the request into a seed of 2 to 80 characters. If the user says "my business" or "my niche", take the seed from the site itself: call `get_seo_organic_keywords` (what the site already ranks for) or `get_seo_overview`, and name the seed you chose.

## Research

3. Tell the user that research spends one of the site's daily lookups, then call `research_keywords` with the `seed`. For "high volume, low competition" use `sort` set to `opportunity`, a `minVolume` the user is comfortable with, `maxDifficulty` of 49 or lower (0 to 29 is easy, 30 to 49 medium), and `newOnly` set to true so keywords already in the list are left out. Add `notTop10` when the user wants gaps rather than keywords they already win. Every row carries the site's own position for that keyword.
4. Present the rows as a short table: keyword, monthly volume, difficulty, intent, opportunity score, the site's current position. Keep the tool's order.

## Save the keepers

5. Before saving, call `check_keywords` with the chosen keywords; it says which already exist in the site's keyword list or already have an article.
6. Call `add_keywords` with the new ones (comma or newline separated, up to 100 at once). To put them in a keyword list, pass `groupName` (a list is created if needed) or a `groupId` from `list_keyword_groups`. This changes the account, so confirm the keywords and the list name first.

## Write the article

7. To write the article yourself in the conversation, call `create_draft_article` with the `title` and `articleType`, then fill it with `update_article`, `append_article_section` or `replace_article_section`. Nothing is published.
8. To have Sight AI write it, confirm that generation spends AI credits, then call `generate_article` with the `targetKeyword` (and `articleType`). It runs in the background: poll `get_article` until the status is ready. Articles generated through the plugin get no AI cover image; tell the user to add one in Sight AI (Content, then Articles, then Generate image) or give an image URL to `set_article_main_image`.
9. Tighten the metadata with `refresh_seo_title` and `refresh_seo_meta` when asked.

## Publish, only when asked

10. Check `get_cms_status` first. If a CMS is connected and the user asks to publish, call `sync_article`, then `submit_article_indexnow` so the new URL is picked up quickly. Both change the live site, so confirm before each.

## Do not

- Do not call `research_keywords` with `refresh` set to true unless the user asks for fresh data; it pays for a new search instead of using the cache.
- Do not save keywords, generate, sync or submit without confirmation.
- Do not promise rankings or traffic for a keyword; report its volume, difficulty and opportunity score as returned.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: fix-site-audit-issues
description: Read a site's technical SEO audit in Sight AI, show what is broken or got worse, find decaying and cannibalized content, and fix title, description, H1, canonical and schema issues on Sight-managed articles with a reviewed before/after. Use when the user asks about site health, audit errors, broken pages, or what to fix on the site.
---

Use this skill when the user wants to know what is technically wrong with the site and fix it. Reads need no confirmation; applying a fix changes a live article and does.

## Pick the site

1. Call `list_sites` and settle on one site. Every other tool takes its `siteId`.

## Read the audit

2. Call `get_seo_audit` for the latest crawl: status, on-page score, error, warning and notice counts, the previous audit for comparison, and the page issues. Use `severity` ("error", "warning", "notice" or "all") and `page` / `limit` to work through the list. Lead with errors.
3. Call `get_seo_audit_comparison` with `status` "new" to show what appeared since the previous crawl, "fixed" to confirm what was resolved, or "persisting" for what keeps coming back.
4. For one URL, call `get_seo_page_detail`: its keywords, rankings, Search Console queries, audit issues, backlinks and AI citations in one place. For the whole site by section, call `get_seo_pages`.
5. Call `get_seo_internal_links` for orphan and weakly linked pages and the suggested links with anchors.
6. Call `get_seo_content_health` with `kind` "decay" for pages losing clicks over the last 28 days with the reasons, or "cannibalization" for queries where several pages compete and the page to consolidate on.

## Fix what Sight manages

7. For a missing or long title or description, a missing H1, a canonical or a JSON-LD problem on an article Sight manages, call `propose_audit_fix` for that issue. It returns a before/after proposal and writes nothing.
8. Show the proposal and wait for the user to approve it. Then call `apply_audit_fix` with the proposal unchanged; the article is updated and re-synced to its CMS. Never apply a proposal the user did not see.
9. Issues on pages Sight does not manage cannot be fixed from here; say what to change and where.

## Re-check

10. To crawl again, call `run_site_audit` (optionally `maxPages`, `enableJavascript`, `lighthousePages`). It is queued and only one audit runs at a time, so tell the user results land in a few minutes and read them with `get_seo_audit` afterwards. Audits spend the site's SEO budget, so ask before starting one.

## Do not

- Do not call `apply_audit_fix` without an approved proposal from `propose_audit_fix`.
- Do not describe an issue as fixed until `get_seo_audit_comparison` or a fresh `get_seo_audit` shows it gone.
- Do not invent page speed or crawl numbers; report only what the tools return.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: publish-and-get-indexed
description: Publish ready Sight AI articles to the connected CMS, schedule them, submit them to IndexNow and Google Search Console, and check index coverage. Use when the user asks to publish or schedule an article, why a page is not indexed, or to get content indexed faster.
---

Use this skill when the user wants an article live or wants Google and Bing to pick pages up. Reads need no confirmation; publishing, scheduling, submitting and inspecting (which spends a daily budget) do.

## Pick the site and the article

1. Call `list_sites` and settle on one site. Every other tool takes its `siteId`.
2. Call `list_articles` with a `status` filter to find the article, and `get_article` for its title, body and SEO fields when the user wants to check it before publishing.
3. Call `get_cms_status` for the active CMS integration, whether the article is eligible to sync, and whether sync is manual-only (Framer). Call `get_article_sync_status` for a per-platform view of an article already synced.

## Publish now or later

4. To publish now, confirm the article and the destination, then call `sync_article` with the `articleId` (and `integrationType` when the user names one). It goes to the live site.
5. To publish later, call `schedule_article` with the `articleIds`, a future `scheduledDate` and optional `scheduledTime`. Call `get_planner` with `view` "scheduled" to show the publish queue, or "settings" for the daily sync limit and default publish time. To move or remove a queued item, confirm and call `update_scheduled_article` or `remove_scheduled_article` with the `queueId`.

## Get it indexed

6. After publishing, call `submit_article_indexnow` with the `articleId` so Bing and Yandex pick it up; `get_indexnow_status` with the `url` shows the submission state.
7. Call `get_gsc_status` for the Search Console connection, and `submit_sitemap_gsc` to resubmit the sitemap when new URLs were added.
8. Call `get_seo_indexing` for coverage from Google URL Inspection: indexed, not indexed, excluded, never inspected and stale URLs with the verdict and advice, plus today's inspection budget. Filter with `state` "not_indexed", "never_inspected" and the others.
9. To check specific pages now, confirm (it spends the daily inspection budget) and call `inspect_urls` with up to 20 `urls`; after a not-indexed verdict, `resubmit_urls` with up to 50 `urls` re-sends them through IndexNow.
10. When something is set up wrong (no CMS, Search Console disconnected, IndexNow key missing), call `get_account_health` and pass on its blockers.

## Do not

- Do not call `sync_article` or `schedule_article` without the user naming the article and confirming.
- Do not promise Google will index a page; report the verdict and the advice the inspection returns.
- Do not resubmit URLs that are already indexed.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: review-backlinks-and-prospects
description: Review a site's backlink profile in Sight AI, spot lost or toxic links, build the disavow file, and work the link prospects (competitor link intersect, unlinked brand mentions, broken links) toward outreach. Use when the user asks about backlinks, referring domains, toxic links, disavow, or where to get links.
---

Use this skill when the user asks about links pointing at the site or how to earn more. Reads need no confirmation; review decisions, refreshes and queuing outreach do.

## Pick the site

1. Call `list_sites` and settle on one site. Every other tool takes its `siteId`.

## The profile

2. Call `get_seo_backlinks` for the summary with deltas against the previous snapshot and the referring pages; `status` "live" (default) or "lost" for recently lost links.
3. Call `get_seo_backlink_profile` with `section` "profile" for the 24-month timeseries and the anchor and velocity health, "anchors" for the anchor text mix, "referring_domains" for every domain with spam score and review state, "toxic" for the candidates with reasons, "new" for links first seen in the last 30 days, or "broken" for links to pages that no longer resolve.
4. Call `get_seo_history` when the user wants the monthly trend of backlinks and referring domains next to organic keywords and traffic.

## Toxic links and the disavow file

5. Walk the toxic list with the user. For each domain they decide on, call `manage_seo_backlinks` with `action` "review", the `domain` and `status` "keep", "disavow", "reviewed" or "none". Confirm the decision first; disavowing is a signal to Google.
6. Call `get_seo_disavow_file` for the disavow text built from the domains marked "disavow", and tell the user it is uploaded in Google Search Console, not by Sight AI.

## Link prospects

7. Call `get_seo_link_prospects` for the prospects on file: `source` "intersect" (domains linking to competitors but not the site), "mention" (unlinked brand mentions) or "broken" (broken links to the site); `status` "open", "added", "dismissed" or "all". The rows include the proof-of-value attribution of links won through outreach.
8. To act, confirm and call `dismiss_link_prospects` or `reopen_link_prospects` with the `prospectIds`, or `refresh_link_prospects` to run the intersect, mention and broken-link scans again (queued). Handing prospects to the outreach agent is done in Sight AI (Backlinks, then Link prospects), not through the plugin.

## Refresh the data

9. Call `refresh_backlinks` to pull the profile again (`mode` "one_per_domain" or "as_is"). It is queued and spends the site's SEO budget, so ask first.

## Do not

- Do not mark a domain "disavow" without the user naming it.
- Do not say an email was sent or that outreach was started; the plugin only dismisses, reopens and refreshes prospects.
- Do not estimate domain authority yourself; use the domain rank and spam score the tools return.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: review-search-performance
description: Review a site's Google rankings and Search Console performance in Sight AI and explain what changed. Use when the user asks how their SEO or organic traffic is doing, which keywords moved, why traffic dropped or grew, or what to fix next.
---

Use this skill when the user wants to know how a site is doing in Google search or why its traffic changed. Every tool here only reads data, so none of them needs confirmation.

## Pick the site

1. Call `list_sites`. If the account has one site, use it. If it has several and the user did not name one, ask which site before calling anything else. Every other tool takes that site's `siteId`.

## Read the data

2. Call `get_seo_overview` for the health tiles, the ranked fix-next actions and the striking-distance keywords. This is the best single summary; start the answer from it.
3. Call `get_seo_rankings` for the tracked keywords with their latest Google position, the 7-day and 30-day change, the ranking URL and competitor positions. Page through with `page` and `limit` when the user wants the whole list.
4. For traffic, call `get_search_overview` with the window the user asked for (`days`), then `get_search_queries` and `get_search_pages` for the queries and landing pages behind it. These come from the site's Google Search Console data.
5. When the user asks why traffic or rankings changed, call `explain_search_change` with the window in `days` (7 to 90, default 28). It compares the window with the same length before it and returns the queries and pages that moved most, lined up with rank moves, lost backlinks, audit error changes and lost Google AI Mode citations, plus a ranked list of likely causes with the numbers behind each. Report those causes in the tool's order.
6. For the alert feed (rank drops, lost page-one positions, lost backlinks, audit errors), call `get_seo_alerts` with `view` set to `feed`.
7. For one keyword's day-by-day history, call `get_seo_keyword_history` with its `keywordId` or `keyword` text.

## Presenting results

- Lead with the change, then the cause, then the suggested action. Quote positions, clicks and impressions exactly as the tools return them, with the window they cover.
- A keyword that "dropped out of the top ten" is one whose latest position is above 10 and whose 7-day change is negative; say both numbers.
- If the SEO module is not on the user's plan, the tool says so and names the plan that includes it. Pass that on and use the Search Console tools, which every plan has.

## Do not

- Do not invent a reason for a change that `explain_search_change` did not return; say the data does not show one.
- Do not estimate traffic value or forecasts from these numbers yourself; `get_seo_forecast`, `get_seo_what_if` and `get_seo_traffic_value` exist for that.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: set-up-alerts-and-reports
description: Configure Sight AI's SEO alert rules, read the alert feed, generate or schedule weekly and monthly SEO reports with share links, annotate the charts, and forecast traffic or the value of ranking gains. Use when the user wants to be notified about rank drops or lost links, wants a report for a client or manager, or asks what a ranking improvement would be worth.
---

Use this skill when the user wants monitoring, reporting or projections. Reads need no confirmation; changing rules, generating or sending reports and adding notes do.

## Pick the site

1. Call `list_sites` and settle on one site. Every other tool takes its `siteId`.

## Alerts

2. Call `get_seo_alerts` with `view` "feed" for the signals in the window (rank drops and gains, lost top 3 or page 1, lost backlinks, audit errors), newest first; `days`, `severity` and `kind` narrow it. `view` "rules" lists the rules and their channels.
3. To change a rule, confirm and call `update_alert_rule` with the `kind` and a `patch` (enabled, threshold, minDomainRank, channelEmail, channelSlack, webhookUrl, digest "instant", "daily" or "weekly"). `send_test_alert` with a `kind` sends a sample through the rule's channels; `mark_alerts_read` clears the feed.

## Reports

4. Call `get_seo_reports` for the weekly and monthly schedules (recipients, sections, white label) and the past reports with their share links. With a `reportId` it returns one report's full payload and narrative.
5. To make one now, confirm and call `generate_seo_report` with `cadence` "weekly" or "monthly" (the last complete period) or a custom `periodStart` and `periodEnd`. The report is stored with a share link; give the link to the user.
6. To set up recurring delivery, call `save_report_schedule` with a `schedule` object: cadence, recipients, sections, and white label (brand name, logo URL, accent, hide Sight branding) for client-facing reports. `send_seo_report` with a `reportId` emails it to the schedule's recipients or the ones given. Confirm recipients before sending.
7. To mark an event on the charts (a site migration, a Google update, a campaign), call `add_seo_annotation` with the `date`, a `label` and `kind` "manual" or "google_update". `get_seo_annotations` lists notes and the derived publish and audit events.

## Forecasts and value

8. Call `get_seo_forecast` for weekly clicks and impressions with the fitted trend and the 4, 8 and 12-week projection.
9. Call `get_seo_what_if` with tracked `keywords` (or ad-hoc keyword, volume, position and CPC rows) and a `targetPosition` for the extra monthly clicks and dollar value on the site's own CTR curve.
10. Call `get_seo_traffic_value` for what the site's organic visits would cost as ads per month, the top pages and keywords by value, and the keywords with the most upside.

## Do not

- Do not send a report or change recipients without confirmation.
- Do not present a projection as a promise; say it is the fitted trend from Search Console data.
- Do not turn alert rules on or off silently; name the rule and the channel.

Referenced files: 1 — file references are metadata, not package contents.