Help

Fix common problems

A directory of symptoms with a fix for each, from Claude not seeing PageSumo to blank pages and domain trouble.

Find your problem below. If a fix doesn't work, each section says when to stop and contact support.

Try these first

Three moves fix most problems:

  1. Fully quit the Claude app and reopen it. Claude only reloads what a connection can do when it restarts.
  2. Wait 60 seconds and hard refresh (Cmd+Shift+R on Mac, Ctrl+F5 on Windows). Published pages are cached briefly, so a fresh update can look stale.
  3. Read the exact message you were shown. Limits, rate limits, and publish warnings all say what they want.

Find your problem

Claude doesn't see PageSumo, or can't publish

What is happening. Claude loads the list of things a connection can do once, when it connects. If you just connected PageSumo, or your connection changed, Claude keeps working from the old list until the app restarts or the connection is made fresh. Claude may also still show a PageSumo tile after you disconnect, even though it can no longer publish.

Fix it:

  1. Fully quit the Claude app and reopen it, then try again. This alone fixes most cases.
  2. Check the connection is live: in the dashboard, open Settings and find the Connect Claude card. It should show a "Claude connected" chip.
  3. If it is not connected, reconnect: in Claude, open the Connectors list, open the PageSumo tile, and click Connect. Sign in when asked.
  4. After reconnecting, restart Claude once more so it picks up the fresh connection.

When to contact support. You restarted Claude, Settings shows "Claude connected", and publishing still fails with an error you don't understand. Include the exact error text Claude showed you.

My page isn't updating after I made changes

What is happening. Two different things can cause this. First, published pages are cached, so a just-updated page can look stale for up to 60 seconds. Second, if you said "publish this" a second time instead of asking Claude to update the existing page, Claude may have created a brand-new page at a new address, leaving the old one untouched.

Fix it:

  1. Wait a minute, then hard refresh the page in your browser (Cmd+Shift+R on Mac, Ctrl+F5 on Windows).
  2. Open Pages in the dashboard and look for a duplicate. If a second copy of the page appeared, Claude published a new page instead of updating the old one. Delete the copy you don't want.
  3. To update in place next time, ask Claude to update the existing page by name, for example "update my pricing page with these changes". An update keeps the same live URL.
  4. You can also update from the dashboard: open the page under Pages, go to the Replace file tab, and upload the new file. The URL never changes when you replace a file.

When to contact support. The page still shows old content several minutes after an update, on a hard refresh, and Pages shows no duplicate.

Warnings Claude might show you when publishing

What is happening. A publish can succeed and still come back with a warning. Warnings are not errors: your page is live, but PageSumo noticed something you probably want to fix. Claude relays them into your conversation, and the dashboard shows the same warnings after an upload. The common ones:

When to contact support. A warning doesn't match anything on this list and you can't tell what it wants, or you fixed what it asked and the same warning keeps coming back. Include the exact warning text.

My page's AI or chat features don't work on the published page

What is happening. A page that talks to Claude, like a quiz or chat assistant built as an artifact (Claude's name for a page or mini-app it builds in the side panel), needs the owner's Anthropic key connected before its AI features work for visitors. The artifact preview inside Claude can also do more than a published page can, so a feature that worked in the preview may not work published.

Fix it:

  1. Connect your Anthropic key: open Settings and find the AI pages card. Once the key is connected, the page starts working with no change to the page needed.
  2. If the key is connected and a feature still doesn't work, see Pages that use AI for what published pages support and how to have Claude rebuild the feature.

When to contact support. Your key is connected, the page uses ordinary Claude messages, and visitors still get errors.

My React page renders blank

What is happening. A page built from a React artifact loads its code libraries when a visitor opens it. The libraries Claude artifacts commonly use, for charts, icons, animation, and dates, load automatically on published pages. If the artifact used an unusual library, it may not be available, and the page's component never starts. When nothing manages to render, the page shows a notice after a few seconds instead of staying silently blank.

Fix it:

  1. Open the published page and wait a few seconds. If a notice appears, it confirms the page failed to start rather than being empty.
  2. Ask Claude to rebuild the page using more common libraries, or as plain HTML, CSS, and JavaScript with no libraries at all, then update the page.

When to contact support. The page renders fine as an artifact in Claude, uses only ordinary libraries (or none), and still comes up blank published.

My image looks different after publishing

What is happening. Images on published pages are optimized for fast loading when served: they can be converted to a modern format the visitor's browser prefers, and very large images are scaled down. Your original file is kept unchanged; the optimization happens on the way to the visitor. A slight difference in file size or crispness on close inspection is normal and makes the page load much faster.

Fix it. Usually nothing needs fixing. If an image must be pixel-perfect, start from a version no larger than it will be displayed, so scaling never applies.

When to contact support. An image is visibly broken, blurry at normal viewing size, or missing entirely after publishing.

A visitor says the password isn't working

What is happening. Changing a page's password immediately locks out everyone who unlocked it before; they are asked for the new password on their next visit. There is also no way to view a page's current password anywhere in the dashboard, so if it has been lost, the fix is a fresh one.

Fix it:

  1. Set a fresh password on the page. See Manage a page for where.
  2. Send the new password to the visitors who need it.

When to contact support. A visitor enters the password you just set, copied exactly, and it still doesn't unlock the page.

"Too many attempts"

What is happening. Several actions in PageSumo are rate-limited to protect your account and the service: signing in, resetting passwords, changing settings, sending support messages, and similar. If you repeat one quickly, you see a message like "Too many attempts. Try again later." Nothing is broken and nothing was lost.

Fix it. Wait a few minutes, then try once more. The limit resets on its own. The account actions this applies to are listed in Your account.

When to contact support. You are still blocked long after waiting, or you see the message on your very first attempt.

I hit my page limit

What is happening. Each plan includes a set number of live pages, and the free plan includes 10. When you publish past the limit you see a message like "You've reached your plan's limit of 10 pages. Delete a page to publish a new one, or upgrade your plan." Updating or replacing an existing page never counts against the limit; only publishing a new page does.

Fix it:

  1. Delete a page you no longer need: open it under Pages, go to Page details, and use Delete. Deleting is permanent, including the page's leads and stats.
  2. Or upgrade: open Settings, then Plan and billing, and choose a bigger plan. Your plan's limit is shown there.
  3. Then retry your publish.

When to contact support. The limit message appears but Pages shows fewer live pages than your plan includes.

My custom domain isn't working

What is happening. A connected domain starts in a verifying state while PageSumo waits for your DNS records to point at us and for the SSL certificate to be issued. The Domains screen tells you which step it is waiting on: "Waiting for your DNS record to point at the IP" means the record isn't visible yet, and a message about issuing the SSL certificate means DNS is found and the last step is in progress.

Fix it:

  1. Open Domains in the dashboard and find your domain's card. It lists the exact DNS records to add at your domain provider: an A record whose Target is the IP address shown on the screen, and, for a root domain like yourbrand.com, a second CNAME record with Host www pointing at your domain.
  2. Add those records at your domain provider or registrar, copying the values exactly as shown.
  3. Remove any conflicting A, AAAA, or CNAME records on those same names, and turn off domain forwarding if it is on.
  4. Click Check status on the domain's card. Once the records are found, allow a few minutes for the domain to initialize and for SSL to take effect, then check again.

If a domain that used to work has stopped, the records at your provider probably changed. On the domain's card, click Show records to reveal the exact records that must stay in place, and compare them with what your domain provider currently shows.

When to contact support. The records are in place and the domain has sat in verifying far longer than expected, or you see "That domain is already connected to another PageSumo account" for a domain you own.

My page is showing "This page is offline"

What is happening. Your plan now includes fewer pages than you have published, usually after a downgrade, so the pages over the limit were paused. Nothing was deleted. Visitors see the offline message, but your own preview from the dashboard still shows the real page. This also happens when a subscription ends after failed payments: the account returns to the free plan and the same pause rules apply. See Upgrade, cancel, or change plans.

Fix it:

  1. Open Pages in the dashboard. A notice at the top explains how many pages are offline, and each offline page is marked Offline.
  2. To bring everything back, upgrade your plan from Settings. Paused pages come back with the upgrade.
  3. To stay on your current plan, pick which page stays live: on an offline page's card, click "Keep this one live". The current live page swaps to offline in its place.

For how limits work across plans, see Plans and limits.

When to contact support. A page shows the offline message even though you are within your plan's limit.

My form isn't capturing leads

Fix it:

  1. Check the form actually collects an email address. A submission with no email-shaped value is ignored on purpose.
  2. Check you updated the page after adding the form. Capture is added at publish time, so a form added to a live page does nothing until you update it.
  3. Ask Claude to "make sure every field in my signup form has a name", then update the page.

When to contact support. The form has a named email field, the page has been updated since, and test submissions still don't appear on the Leads screen.