Troubleshoot AI, previews, analytics, and Smart Paste

OAuth or client cannot connect

1. 1Confirm the endpoint is exactly https://go.simpurl.click/mcp and that the client is configured for remote HTTP MCP, not a local stdio command.
2. 2Confirm AI connections are Enabled in Personal -> Settings -> AI connections and that the account is still eligible.
3. 3Complete the SimpURL browser sign-in in the same account that owns the SimpURL links. SimpURL uses Clerk for that sign-in; do not paste a session token or API key into the client.
4. 4If the connection is shown as Expired or Revoked, use Renew in SimpURL, then reconnect or reauthenticate in the client.
5. 5If the client reports that the server is unavailable, check whether that client, plan, workspace role, region, and surface supports custom remote MCP. OpenAI documents that availability and action support vary by those factors.

A shared link has a stale or missing preview

SimpURL serves crawler-specific metadata for shortened links. It uses the destination page's Open Graph metadata when available, while the canonical share URL remains the SimpURL link. A normal browser redirect and a social preview request therefore follow different paths.

Preview metadata is cached. The backend has a short process-local cache and a shared Redis cache with a default 24-hour TTL for successful destination metadata. The social platform receiving the link can also cache its own card independently.

1. 1Verify the destination page has the intended OG title, OG description, and OG image, and that the image is publicly reachable over HTTPS.
2. 2Open the SimpURL link in a normal browser to confirm the human redirect still works. A preview crawler should not be treated as a human click.
3. 3Use the sharing platform's official link-debug or scrape-refresh control when it offers one. Reposting the same URL may continue to show that platform's cached card.
4. 4If the destination or link was just changed, allow the preview caches to expire and retry. Do not infer that a stale card means the redirect target is stale.
5. 5If the link is expired, archived, unavailable, or blocked by the destination, fix that state first; a crawler cannot build a valid card from an unavailable target.

Analytics do not match another platform

SimpURL records redirect and page events under its own event rules. It normalizes referrers to source hosts, excludes known preview crawlers, and may see no referrer when the browser or platform strips it. The MCP report is aggregated and intentionally omits raw IP addresses and user-agent strings.

Treat SimpURL analytics as a directional measurement layer, not a 1:1 mirror of impressions, views, clicks, or conversions reported by a social, email, ad, or destination platform. Compare the same link, time zone, attribution window, and event definition before investigating a difference.

• Check the selected range: supported values are 7, 14, 30, 90, and 180 days, subject to plan caps of 14 days for Free, 90 for Starter, and 180 for Pro or Business.
• Check whether the request is account-wide or campaign-scoped. Campaign history follows current link membership in the campaign report.
• Check for excluded referrer domains or privacy tools that remove referrer, browser, or operating-system signals.
• Check whether the client hit an analytics rate limit of 15 calls per minute. Retry after the returned limit window instead of issuing a rapid loop.

A profile or Page is unavailable

1. 1For a profile, confirm it is marked public, the handle is correct, the account still has profile access, and scheduled profile links are currently visible. A private profile returns an unavailable response rather than exposing its content.
2. 2For a Page, confirm it is published and not archived. Draft edits live in the editor and do not become public until Publish; a draft or unpublished revision is not a public Page.
3. 3When testing a Page or profile share card, test the public URL as a signed-out visitor. A dashboard preview and a public crawler request are different contexts.
4. 4If the public URL returns unavailable after publishing, retry the public URL and check the slug, publication state, plan access, and service status before changing content.

Smart Paste does not run in Chrome

1. 1Open a normal HTTP or HTTPS publishing site, open the Smart Paste popup, and confirm the active host is shown. Chrome internal pages and unsupported pages cannot run the content script.
2. 2Confirm you are signed in to SimpURL in a normal browser tab. The extension reuses the existing Clerk session; it does not store a Clerk token in chrome.storage.
3. 3In the popup, choose Enable on this site and approve Chrome's one-time site-access prompt. A site saved in SimpURL can still show Access needed until this browser permission is granted.
4. 4If the site is configured by a wildcard, grant access for the exact host where you paste. A wildcard Smart Paste setting does not itself grant Chrome access to every matching site.
5. 5After changing permissions or updating the extension, use the popup refresh and reload the active tab if the editor was already open. The background worker re-registers scripts on permission changes, startup, and update, and injects the current tab when enabling a site.
6. 6If paste still fails, check that the site is enabled, the plan supports Smart Paste, the page has a text input, textarea, or contenteditable editor, and the extension can reach SimpURL. The original paste should be restored if the service cannot respond.