Glossary

This page defines terms used throughout SitePulse that may not be self-explanatory.

A

Accessibility score — SitePulse passes Lighthouse's axe-based accessibility audit and reports the raw 0–100 score. See Accessibility.

Alert threshold — A score floor you set per category (e.g. "SEO must stay above 70"). When an audit result crosses that floor, SitePulse sends an alert. See Alert Thresholds.

Applied patch — A CMS patch that has been written back to your CMS (WordPress / Webflow / Drupal). The UI shows applied patches in a separate section from pending ones.

Audit — A full evaluation of a target (URL, sitemap, GitHub repo, or competitor). Produces an AuditResult per scored category.

B

Best Practices score — Lighthouse's best-practices audit (HTTPS, deprecated APIs, etc.). See Best Practices.

Brand Radar — The feature that tracks topic extraction, sentiment, and Share of Voice over time across brand mentions. See Brand Radar.

Brand Voice — A set of Vale lint rules and tone guidelines associated with a project. Used to generate brand_voice_fix rewrite suggestions. See Brand Voice.

BYOK — Bring Your Own Key. Configure your own Anthropic or OpenAI API key so SitePulse uses it for AI operations instead of the system key. See BYOK.

C

Citability — A component of the GEO score measuring how well-cited your content is — whether it attributes sources, uses quotes, and provides factual anchors that AI search systems can verify. Part of the GEO rubric at 10 points.

CMS patch — A rewrite suggestion that can be automatically applied to your CMS (WordPress/Webflow/Drupal). Not all suggestion types support auto-patching. See CMS Patches.

Competitor audit — An audit that compares your project domain against one or more competitor domains. See Competitor Audit.

Content Quality score — A 100-point rubric measuring readability, depth, structure, engagement, and technical quality of page content. See Content Quality.

CTR — Click-Through Rate. The percentage of Google Search impressions that result in clicks. Displayed per-URL when Google Search Console is connected.

D

Deep Blue — SitePulse's brand primary color (oklch(0.437 0.196 258.0)), a deep indigo used for primary actions and score gauges.

Dead anchor — A /docs/... link in an MDX file that does not resolve to a registered page in nav.ts. Caught by the lint-links CI script.

E

Excerpt — A 200-character plain-text snippet derived from page body content. Used in search results and social preview cards.

F

Flesch Reading Ease — A readability score (0–100) computed from sentence length and syllable count. Higher = easier to read. Scores above 60 are considered readable for general audiences. Used in the Content Quality rubric.

Free tier — SitePulse's no-cost plan with 1 project and 5 URL audits per month. See Billing & Plans.

G

GEO — Generative Engine Optimization. The practice of making content more visible and cite-able in AI-generated answers (ChatGPT, Perplexity, Google AI Overviews, etc.). SitePulse's GEO score is a 100-point rubric. See GEO Score.

GEO lint — A set of 35 signal-level rules that evaluate GEO-readiness at the HTML level (schema presence, heading structure, citation markers, etc.). Part of the GEO rubric at 10 points.

GEO probe — A synthetic query sent to one or more AI providers (Perplexity, OpenAI, Anthropic, Gemini) to test whether your brand/domain is mentioned in AI-generated answers. See GEO Visibility.

GEO strategy — One of 9 AI-specific improvement strategies SitePulse can recommend: cite_sources, add_quotes, add_statistics, add_authority, fluency, simpler_language, unique_words, add_keywords, ease_of_understanding.

GitHub audit — An audit that analyzes a GitHub repository for content quality and SEO/GEO signals across all text files. Requires an Anthropic key (Claude Agent SDK). See GitHub Audit.

GSC — Google Search Console. When connected, brings real impression/click/CTR/position data into SitePulse. See Google Search Console.

H

Hit rate — In GEO probes, the fraction of queries where your brand or domain appeared in the AI-generated response. Used to normalize the GEO trend chart.

I

Impressions — The number of times a URL appeared in Google Search results (regardless of clicks). From Google Search Console data.

J

JSON-LD — JavaScript Object Notation for Linked Data. The recommended format for Schema.org structured data. SitePulse's schema checker looks for <script type="application/ld+json"> blocks. Part of the GEO and SEO rubrics.

K

Key resolution order — For BYOK: SitePulse uses (1) project-level key, (2) user-level key, (3) system key. See BYOK.

L

Lighthouse — Google's open-source auditing tool. SitePulse runs Lighthouse (via PageSpeed Insights API) to score Performance, SEO, Accessibility, and Best Practices. The raw Lighthouse score is passed through for these categories; SitePulse adds its own rubric on top for SEO and GEO.

M

MCP — Model Context Protocol. An open standard for connecting AI assistants to external tools. SitePulse exposes an MCP server at https://app.sitepulse.app/mcp. See MCP Server.

Metric — An individual measurement within an audit (e.g. lcp_ms, reading_ease, brand_avg_rank). Stored as AuditMetric records and used for trend charts.

O

Organization — A team workspace in SitePulse. Projects belong to an organization. Members share access to all projects in the org. See Organizations.

P

Pending rewrite — A rewrite suggestion with status pending — not yet approved, rejected, or edited.

Performance score — Lighthouse's Core Web Vitals-based performance score (0–100). See Performance.

Persona — A content_persona entry on a project that describes a target audience. Active personas are injected into AI analysis to produce persona-relevant rewrite suggestions. See Personas.

PKCE — Proof Key for Code Exchange. A security extension to OAuth 2.1 that SitePulse uses for Webflow OAuth. See Webflow OAuth.

Plan limits — Per-organization limits on audits, projects, and seats by billing plan. See Quotas & Limits.

Q

Quota — A usage counter tracked in Redis, reset at the start of each billing period. Soft warning at 80%, hard block at 100%. See Quotas & Limits.

R

RBAC — Role-Based Access Control. SitePulse roles: Owner, Admin, Member. See Roles & Permissions.

Rewrite suggestion — An AI-generated recommendation to improve a specific piece of content. SitePulse has 20 suggestion types. See Rewrites.

Rubric — A structured scoring breakdown into weighted sub-dimensions. SitePulse uses 100-point rubrics for GEO, SEO (custom portion), Content Quality, and Accessibility.

S

Scheduled audit — An audit that runs automatically on a set cadence (daily/weekly/monthly). See Schedules.

SEO score — A composite of Lighthouse's SEO pass-through (40 pts) and SitePulse's custom 60-point SEO rubric. See SEO Score.

Share of Voice (SOV) — The fraction of brand mentions in a topic category that belong to your domain vs. competitors. Expressed as a percentage per topic, per time window. See Share of Voice Explained.

Sitemap audit — An audit that processes every URL in a sitemap.xml file and aggregates results. See Sitemap Audit.

Slug — The URL path segment after /docs/. For example, reports/geo is the slug for /docs/reports/geo.

Structured data — Machine-readable markup (Schema.org JSON-LD, Microdata, or RDFa) embedded in a page. SitePulse detects and validates JSON-LD blocks as part of GEO and SEO scoring.

T

Topic bubble — In Brand Radar, a circle whose area represents the number of brand mentions for a given topic cluster, colored by net sentiment.

Trend — A time-series chart of score history for a project. Available per-category (SEO, GEO, etc.) over configurable date ranges. See Trends.

U

URL audit — An audit of a single URL. The most common audit type. See URL Audit.

V

Vale — An open-source prose linter used by SitePulse's Brand Voice feature to enforce tone, style, and phrasing guidelines against a set of rules.

W

Webhook — An HTTP callback SitePulse sends (or receives from Stripe) when specific events occur. Stripe webhooks are used to sync subscription state. See Stripe Checkout & Portal.