You've got a piece that's been published for a while. Traffic's declining, or maybe it never took off in the first place. The question lands on your desk: should you refresh this content or start from scratch?
It's a question the ércule team gets from clients all the time. And honestly, the answer isn't always obvious. A refresh takes less time but might not move the needle. A rewrite is a bigger investment but could deliver better results. The trick is knowing which approach makes sense for each piece.
When to refresh existing content
A refresh works when the bones of your content are solid but the execution needs updating.
Refresh when you see these signals:
Your content is ranking somewhere on page 2 or 3 of search results. It's close to breaking through but needs a push. The topic is still relevant and searches haven't changed dramatically since you published. The core argument or information is sound, but examples are outdated, statistics are old, or the presentation feels stale.
The refresh process is straightforward. Start by updating any time-sensitive information like dates, product versions, statistics, or screenshots. Then look at your on-page SEO. Is your title tag still competitive? Are you targeting the right keywords based on current search data? Check your internal linking structure and add connections to newer, related content on your site.
From there, strengthen weak sections. If a paragraph feels thin or unclear, expand it. If you're missing a use case that competitors cover well, add it.
One practical approach: pull up Google Search Console and look at which queries are driving impressions but not clicks. That's often a sign your meta description or title needs work. Or check which queries are driving clicks but have low average position. Those are opportunities to strengthen specific sections of your content.
Example: Refreshing a comparison post
Say you published "GraphQL vs REST APIs" eighteen months ago. It ranks on page 2 for "graphql rest comparison" and gets decent impressions but few clicks. The content is fundamentally sound, but the code examples reference deprecated syntax and you're missing a section on error handling that competitors cover. A refresh would update the code samples, add the missing section, revise the meta description to be more compelling, and add internal links to newer posts about API design patterns. Potential payoff: jumping from position 12 to position 5.
Example: Refreshing evergreen content
Your "Introduction to Container Orchestration" post from 2022 still gets traffic, but screenshots show an old Kubernetes dashboard UI. The concepts are timeless but the visuals are dated. Refresh the screenshots, update any version numbers mentioned, add a note about recent features like Gateway API, and you've extended the post's shelf life by another two years.
When to rewrite from scratch
Sometimes a refresh won't cut it. A full rewrite makes sense when the content has fundamental problems that can't be fixed with updates.
Rewrite when you're dealing with content that was built around a keyword but lacks a clear purpose or value for readers. Or posts that predate a major shift in your product positioning or target audience. Or pieces where the structure itself is broken. Maybe it's organized poorly, buries the main point, or tries to cover too many topics at once.
A rewrite also makes sense if you're seeing strong search volume for a topic but your existing content isn't competitive. Maybe competitors have published comprehensive guides while you've got a thin blog post. In that case, updating what you have might feel like rearranging deck chairs.
The rewrite process starts with research. What's ranking now for your target keywords? What questions are people actually asking? What format works best? Don't just look at your old content and try to make it better. Look at what's working in the search landscape and build something that can compete.
Then rebuild from the ground up. You might salvage some paragraphs or examples from the old version, but you're creating a new outline, new structure, new flow.
Example: Rewriting for repositioning
Your company originally positioned itself as a database tool but has pivoted to being a complete data platform. The old "How to Choose a Database" post is getting traffic, but it reinforces outdated positioning and ignores half of what the product now does. The structure is built around database selection criteria when it should be about choosing a data infrastructure. This needs a complete rewrite with a new angle, new examples, and new use cases that reflect the current product.
Example: Rewriting to compete
You have a 600-word post called "What is Observability?" that ranks on page 3. The top results are all 3000+ word comprehensive guides covering history, implementation, tools, best practices, and case studies. Your post defines the term and stops. No amount of refreshing will make this competitive. You need to rebuild it as a proper pillar page with depth and structure.
Example: Rewriting structurally broken content
An engineer wrote a tutorial that jumps between concepts without clear progression. It assumes knowledge readers don't have, then explains basic concepts they already know. The information is technically accurate but pedagogically broken. Refreshing won't fix bad teaching. You need to rebuild with a clear learning path, consistent difficulty level, and logical sequencing.
The ROI question
Which pages should you update first, regardless of whether you're refreshing or rewriting?
Focus on content that has real traffic potential or conversion impact. A small improvement to a high-traffic page delivers more value than a perfect rewrite of a page that gets 10 visits a month. Look at pages that are already getting decent traffic but aren't converting well, or pages that rank on page 2 for high-value keywords.
The ércule team calls high-performing pages with optimization potential "Star" pages. The ércule app automatically groups and highlights these. But you can identify them manually too by balancing your Google Search Console data (impressions, clicks, position) with your GA4 engagement and conversion metrics.
Making evergreen content last
Whether you refresh or rewrite, think about longevity. Timely content needs frequent updates by definition, but there's a lot of content that could be evergreen with the right approach.
Strip out unnecessary dates from titles. Instead of "Best Practices for Content Marketing in 2024," use "Best practices for content marketing." Reference principles and frameworks that don't change, not tools or features that might be deprecated next quarter. When you do need to reference something time-sensitive, contain it to a specific section that's easy to update.
This doesn't mean everything should be evergreen. Some content needs to be timely to be valuable. Industry trend roundups, yearly comparisons, news analysis. But a lot of content gets stuck with unnecessary expiration dates. A refresh or rewrite is a good opportunity to fix that.
Technical check-ins matter too
Don't skip the technical side when you're updating content. Run a quick check on page speed, especially if you've added images or embedded media. Make sure internal links aren't pointing to redirected or dead pages. Check that your schema markup is still appropriate if you've changed the content structure.
If you're doing a deeper content audit across your site, consider running a technical SEO audit to catch issues that might be holding back even your best-written pages. Broken links, redirect chains, and indexing problems can undermine good content.
Where does this fit into your content system?
Most teams cobble together their update process from habit and the occasional crisis. Writers rely on memory to remember which posts need refreshing. Someone notices traffic dropping and flags it in Slack. Updates happen when someone has time, not when they're most needed.
A content system replaces that improvisation with a repeatable engine. It formalizes how you keep your content library fresh through scheduled audits and systematic updates. It turns maintenance from a reactive scramble into a predictable part of your operation.
Your content system should include three elements for managing updates.
People and roles
Content updates touch multiple functions. Product marketers know when messaging shifts. Writers understand content quality. Analysts spot performance issues. Engineers flag broken links or slow pages. A strong system clarifies who's responsible for what.
Define who identifies pages needing updates, who makes the refresh-versus-rewrite decision, who does the work, and who reviews before republishing. Spread responsibility intelligently so updates don't bottleneck on one person. When people understand their role in keeping the library fresh, the work becomes more focused and moves faster.
Processes that scale
A maintenance process describes how updates move from identification to completion. It includes how often you audit performance data, what criteria trigger an update, how you prioritize which pages to tackle first, and what workflow the actual update follows.
Document these processes. If you're refreshing product screenshots across multiple posts, should you batch them together or handle them individually? When a product feature gets deprecated, how do you find all the content that references it? Clear processes eliminate the wasted energy spent figuring out how to do recurring tasks.
Most content systems include quarterly or bi-annual audits depending on content volume and how quickly your industry changes. The cadence matters less than the consistency. Schedule the work and it gets done. Leave it to chance and it doesn't.
Technology that supports the workflow
Use tools to surface insights and automate repetitive tasks. Analytics platforms identify declining pages and optimization opportunities. The ércule app tracks performance across your entire library and surfaces update candidates automatically. Project management tools keep update work visible alongside new content production.
Every tool should map to a specific workflow and solve a real bottleneck. When you're manually checking hundreds of pages for broken links or outdated screenshots, automation makes sense. When you need to remember which posts performed well six months ago, tracking tools help.
AI as an accelerant, not chaos
AI can help with content updates, but only if your system provides structure. If your workflows are inconsistent, AI will scale the inconsistency. If your quality standards are unclear, AI amplifies the confusion.
A strong content system allows AI to become useful. Use it to identify pages with outdated information, draft refreshed sections based on new data, generate updated meta descriptions, or check for broken links. But the system determines what gets updated, ensures quality, and maintains your brand voice.
So should you refresh or rewrite?
It depends on whether the content's foundation is solid or broken. Refresh when you've got good content that needs updating. Rewrite when you need to rebuild from scratch to compete.
But more importantly, pick the pages worth updating at all. Not every piece of content deserves the effort. Focus your time on the pages that can actually move the needle for your business.
The work of content optimization is continuous. Your content system should include a regular cadence for reviewing and updating pages, not just creating new ones. Because often, improving what you already have delivers better ROI than publishing something new.
FAQ
How do I know if a page is worth updating at all?
Look at traffic potential and conversion impact. A page that gets 50 visits a month and ranks position 15 for a high-volume keyword is worth updating. A page that gets 5 visits a month and ranks position 45 for a low-volume keyword probably isn't. Check Google Search Console for impressions. High impressions with low clicks means the page is showing up in search but not attracting visitors. That's an update candidate. Also consider strategic value. If a page supports a current campaign or product launch, it might be worth updating regardless of traffic.
Should I update the publish date when I refresh content?
It depends on how substantial the changes are. If you're doing a light refresh with updated screenshots and stats, keep the original publish date. If you've rewritten significant sections, added new information, or changed the structure, update the date. Google cares more about content freshness than publish dates, but readers often use dates to judge relevance. Some teams add an "Updated on" date at the top while keeping the original publish date visible. That works too.
How often should I audit my content for updates?
Quarterly audits work for most teams. Bi-annual audits make sense if your industry moves slowly or your content library is small. Monthly audits might be necessary if you're in a fast-moving space like crypto or AI. The cadence matters less than consistency. Set a schedule and stick to it. Between audits, flag pages opportunistically when you notice issues or when product changes require updates.
What if I don't have good traffic data for older content?
You can still make informed decisions. Use Google Search Console even if you don't have GA4 data. It shows you impressions and clicks going back 16 months. Run a site crawl with Screaming Frog to identify technical issues like broken links or missing meta descriptions. Review the content manually against what's currently ranking for your target keywords. If your competitors have published better content on the same topic since you published, that's a signal. Use the Wayback Machine to see what the SERP landscape looked like when you originally published versus now.
Can I do a partial rewrite instead of choosing between refresh and full rewrite?
Yes, and this is actually pretty common. Maybe 70% of the content still works but one section needs to be completely rebuilt. Or the introduction and conclusion are solid but the middle three sections need restructuring. Treat it like a rewrite for the broken parts and a refresh for the rest. Just make sure the new sections integrate smoothly with what you're keeping. Sometimes a partial rewrite reveals that the whole thing needs rebuilding, so be prepared to escalate if needed.
Do I need to redirect if I'm completely rewriting a page?
Usually no. If you're keeping the same URL and the topic is fundamentally the same, publish the new version at the existing URL. You'll preserve the page's authority and ranking history. Create a redirect only if you're changing the URL or if the rewrite changes the topic so substantially that the old URL doesn't make sense anymore. For example, if "How to Choose a Database" becomes "How to Choose a Data Platform," you might keep the URL or you might redirect to a new, more accurate one. Consider whether existing backlinks and references will still make sense pointing to the new content.
