Social feeds
Squarespace Instagram feed not updating: diagnosis and fixes

Last updated · A-Widget
On this page8
Squarespace Instagram feed not updating: identify the route
Record what you see: missing block, old posts, wrong account or an error. Note whether the issue occurs in the editor, the public page or both. Compare with the real Instagram source rather than assuming the newest content is allowed for the feed.
For a native block, use the current Squarespace Instagram block guide. For a hosted embed, use that vendor's current diagnostics. Their refresh and permission rules are not interchangeable.
Check current integration support
Squarespace now documents a professional Instagram account for its native block. An old personal-account tutorial may describe a route that no longer applies. Confirm the source account and current official instructions before renewing access.
The native guide also describes content-type limits and interval-based refresh. A pinned or unsupported item may not appear as you expect. Do not treat every difference from the Instagram profile as a failed connection.
Inspect account access and connection
Check the planned profile in the site's connected accounts. Confirm that the person renewing access is using the right account. A successful approval of another profile can produce a working display with the wrong content.
Follow Squarespace's current connection-check and reset steps for a native block. For a third-party widget, inspect its own account state and plan. Do not revoke unrelated permissions or disconnect every social account as a general experiment.
Keep a record of the observed error. It helps distinguish an account problem from a page-placement issue. Avoid sending passwords or tokens in a support request.
Instagram feed not updating: check the public page and cache
Open the public page while signed out. Compare it with the editor and, for hosted widgets, the vendor's own display. If the vendor has current posts but the website does not, inspect publication and the relevant cache layer.
Allow for the documented refresh interval. Squarespace notes that native Instagram blocks update periodically rather than instantly. A new post missing immediately after publication is not enough to establish an outage.
Compare the page in a separate browser profile to see whether an extension blocks the feed request. Keep unrelated protections in place. Inspect the request and consent state before changing the connection or adding another block.
Reconnect safely
Keep the existing page setup before changing the connection. Follow the official renewal route and verify the planned profile afterwards. Then save and inspect the public result.
Replace a native block only when the current guide calls for it. Work on the known placement. Avoid adding a second hosted widget merely to conceal the first failure. One planned route is easier to maintain.
Escalate with useful details
Give support the page address and the route you use. Include the exact error and the last allowed source post you expected. Include the time of the observation. Do not claim a vendor-wide outage unless a dated official status source shows it.
Keep private account details out of public support posts. A source profile and error text can often describe the issue without exposing credentials or personal data.
Use a fallback feed or profile link
Keep a normal Instagram profile link while the issue is unresolved. Leave key service details in website content. A feed failure should not hide contact details or business hours.
Use the Squarespace setup guide when rebuilding the route. The Instagram widget reference helps decide whether a simpler link or post embed would meet the task.
Keep a small fault record
Write the page address and what you saw. Note the source post you expected and whether it fits the current display rules. This gives the next check a clear starting point.
Then note where the fault appears. Is it in the native block, a hosted vendor view or only the public page? Those are distinct layers. A source connection fix will not solve every page-cache issue.
Change one known part and inspect the result. Keep the old code or setting available for rollback. If the change does not address the observed cause, do not add another feed over the first one.
Leave a normal source link while you work. The site can remain useful without pretending the feed is current. Do not claim a wider outage unless an official source proves it.
Continue with the right task
FAQ
Should I reconnect every account when one feed is stale?
Identify the source of that display first. A native block and a hosted embed use different account routes. Check the actual error and follow that route’s current help. Changing unrelated connections can disrupt working displays without fixing the stale one.
What should I send to support?
Provide the public page address, the native or vendor route and the exact error. Describe the last expected source post and whether the vendor view is current. Remove private account details and secrets. This gives support a specific failing step to investigate.