Blog / Framer & site building /
How to manage unpublished Framer pages during a redesign
A redesign is underway. Someone shares a preview link for feedback. Someone else digs an old draft route out of a chat thread and assumes it’s the live one. A week later, nobody’s quite sure which pages are public.
Redesigns breed unpublished pages and preview URLs. Lots of them. And unless the team knows which ones are safe to share, things get messy fast.
So treat them as part of the migration plan, not an afterthought. Decide who can preview, what’s public, where feedback goes, and what happens to draft URLs after launch.
Inventory the pages and their state
List the existing live URLs, pages being rebuilt, new drafts, CMS items and temporary review routes. Record the owner, purpose, publication status and intended destination for each. A page can be present in the project without being ready for visitors; the plan should make that distinction obvious.
Group pages by action: keep live, replace at launch, publish later, merge, retire or keep private. Ask the content owner to approve decisions for current offers, policy details and product claims. Do not leave a page public simply because it is difficult to remove, and do not retire a page without checking whether people still rely on it.
Check for duplicate versions in the Framer project. Draft pages with similar names can be mistaken for the approved one. Use clear internal labels, but remember that a page name is not a security setting. I like that sentence enough to say it in every redesign kickoff.
Control preview access
Use Framer’s intended preview and collaboration controls, and understand who can access the project and preview. Share review links only with people who need them. If the page contains private or unpublished information, confirm that the preview is not publicly accessible before using it for feedback.
Don’t rely on an unlinked URL being secret. I never treat “nobody knows the link” as privacy. A preview link can be forwarded, logged or discovered through another route. Follow the project owner’s access and confidentiality rules, and remove temporary access when review ends.
Collect comments in one agreed place. Ask reviewers to identify the page, issue and expected correction. Avoid making parallel edits to duplicate drafts without recording which version is authoritative.
Prevent accidental publication
Before publishing, review the page list and the publish settings. Confirm that only approved pages are exposed and that draft content is not included through a CMS collection, navigation menu or generated archive. Test the live domain after publishing rather than assuming that preview visibility and production visibility match.
Check page titles, robots directives, canonical behaviour and sitemap output for pages that should be indexed. Pages used only for review or staging should not accidentally appear in search. Use the platform’s actual controls and test the rendered output; a note in the project does not prevent indexing.
If a preview page has been shared publicly and needs to be withdrawn, ask the project owner to remove access or change its status, then test the route. A page that is not in the navigation may still be reachable directly.
Coordinate the old and new routes
For every live page replaced in the redesign, decide whether to preserve its URL or redirect it. Map old routes to relevant destinations and test redirects after launch. Don’t point every removed page to the homepage. Keep a list of exceptions where the replacement is not ready.
Update internal links, CMS relationships and menu items to the approved pages. Search for references to old routes in the project and the content library. A draft page should not become the target of a public call to action by accident.
Close the review cycle
When feedback is resolved, mark the approved page clearly, publish through the agreed process and archive or remove obsolete drafts. Keep the decision record with the project. After launch, sample the live routes and check that no temporary pages or preview links remain exposed.
Keep unpublished work private
Preview links are useful because reviewers can see a page in context, but convenience can make access easy to forget. Decide who needs the link, how long it should remain available and whether the preview exposes anything that should not be public. Do not place confidential information in a draft merely because the route is not linked from navigation. A guessed or forwarded URL can travel beyond the original review group.
When the new design replaces existing pages, make a route map before changing slugs. Record which URLs stay, which move and which should be retired. The redirect decision belongs to the migration plan, not to a last-minute cleanup. If a draft page is only temporary, make its status unmistakable in the project and in the review request so nobody treats it as approved copy.
One reviewer should own the final publish decision. Gather feedback in one place and resolve conflicting comments before changing the live project. Afterwards, revisit the old route list and test the important destinations. This is less about creating paperwork than giving the team a clear answer to three questions: what is public, what is still under review, and who can approve the next change?
Use a simple status for each page: draft, in review, approved or published. The status should be visible to everyone who might open the project, and the person changing it should update it as work moves forward. For temporary pages, include the intended removal or review point. This avoids the common ambiguity where a polished preview looks final even though legal, content or technical review is still open.
Related reading
- Creating a pre-publication checklist for Framer CMS editors
- Image alt text in a framer publishing workflow
- Keeping campaign pages manageable in a Framer project
A tidy review process protects both unpublished work and useful old URLs. Before your next redesign publish, open the Framer pages panel and give every page one of those four statuses. Which page could you not label with confidence?