Key Takeaways
Treat web content as a managed product, not launch-day copy
Plan the whole lifecycle. Content strategy is the practice of planning the creation, delivery, and governance of useful, usable content. It covers more than wording: it asks what content is needed, how people will find it, who will produce and approve it, and how it will be maintained. The book's central complaint is that organizations routinely postpone content until design and development are nearly finished. Then writers, reviewers, and publishers are rushed, and quality suffers.
The product analogy usefully shifts attention from a single launch to an ongoing service. In software design, a feature is not complete merely because it has shipped; it must work for real users and be supported over time. Content deserves the same operational seriousness. Still, treating content as an asset should not become a license to accumulate it. An asset earns its place through continued usefulness, not through the effort or expense once spent creating it.
Remove pages that serve neither a user task nor a business goal
Less content, less drag. The book offers a simple test: web content should support a business objective, help a user complete a task, or both. A client who wanted a large site in hopes of improving search rankings and standing apart from competitors illustrates the trap: volume also brings creation and upkeep costs, while making useful information harder to find. Too many choices can overwhelm visitors, and weak site search can turn a large library into a maze. Pruning irrelevant or outdated pages frees resources for useful work, including planning and measurement.
This is a practical antidote to the assumption that more information automatically means more value. Human-computer interaction research often treats attention and decision effort as scarce resources, making clarity a meaningful design advantage. Yet aggressive reduction can hide useful depth, especially for expert audiences or complex decisions. The better rule is not simply to make sites small. It is to make every page prove its purpose, then organize essential detail so visitors can reach it when they need it.
Count every page, then judge whether each deserves to stay
Inventory before redesign. A content audit is a systematic account and assessment of an organization's online material. Its quantitative side records what exists and where it lives, including pages, downloads, videos, and dynamic modules. Its qualitative side asks whether the material is accurate, useful, readable, current, and relevant to users and business goals. The book urges teams to inspect deep pages, not just polished home pages, where neglected information often accumulates. For large sites, a rolling inventory can be more practical than trying to capture a perfect snapshot all at once.
An inventory converts a vague complaint into an inspectable system. That is valuable in any complex operation: what cannot be seen is difficult to prioritize, budget for, or assign. The ratings, however, are not objective merely because they appear in a spreadsheet. Teams need shared criteria, and subject experts may need to verify claims. Analytics can reveal use, but low traffic alone does not prove that a page has no value. Audit evidence should inform judgment rather than impersonate it.
Separate the outcome you need from the feature someone requests
Define the real objective. During analysis, the team clarifies what the organization hopes to achieve, what users need, how success will be measured, and what time, skills, and budget are available. A request for a blog or a prominent executive photo is a tactic, not an objective. Business goals, project requirements, and restrictions also need to be distinguished from the specific outcomes a project can deliver. The resulting strategic foundation documents objectives, assumptions, success measures, and risks so stakeholders can agree on reality before recommendations are made. Research should include internal processes as well as users, competitors, communication channels, and relevant external conditions.
This distinction resembles systems analysis: a proposed feature is one possible intervention, while an objective describes the change the system is meant to produce. It helps teams avoid mistaking visibility for impact. The process also recognizes that stakeholder requests contain useful information, even when the requested solution is poor. A danger is that formal objective-setting can privilege what is easy to measure. Teams should pair measurable targets with qualitative evidence about whether the experience actually helps people.
Map each page to a message, a task, and a responsible source
Turn strategy into specifications. Recommendations should connect business objectives and user needs to concrete content: what each page says, how it is structured, and where its source material comes from. The book describes a message hierarchy: a primary idea, supporting messages, the facts that substantiate them, and an action the visitor can take. Page tables document a page's purpose, source content, requirements, and maintenance needs, complementing site maps and wireframes. Teams should also plan labels, formats, links, content types, and metadata. A proposed article or feature that serves no defined message or user task is a strong candidate for removal.
The emphasis on traceability is a strong bridge between strategy and production. In complex design work, decisions are easier to maintain when each element can be linked to a user need and an organizational purpose. Page-level documentation also exposes feasibility questions before production begins. A message hierarchy is a useful editing tool, but visitors do not always follow a linear narrative. Clear navigation, contextual links, and page-level usefulness matter as much as a carefully arranged argument.
Design a human workflow; a CMS cannot approve truth
Make responsibility visible. A content workflow maps how material is requested, sourced, created, reviewed, approved, published, and eventually updated or removed. It identifies the people and tasks at each step: requesters, subject experts, creators, reviewers, approvers, and publishers. This matters because content work is routinely underestimated. One example describes a reviewer receiving a 225-page support document with roughly a day to examine it. A realistic workflow sets responsibilities, handoffs, notification rules, approval steps, and time estimates. It should be designed around the actual people and constraints, rather than assumed to emerge from the content management software.
The workflow view treats quality as a property of coordination, not just individual talent. That is consistent with safety-critical fields, where clear handoffs and explicit authority reduce preventable errors. Yet process can become its own obstacle: too many reviewers or mandatory approvals can slow routine updates and dilute accountability. A useful workflow distinguishes high-risk material, such as legal or safety claims, from low-risk edits, and gives one accountable editor the authority to resolve deadlocks.
Hire web writers to solve reader problems, not fill boxes
Writing includes design work. Web writing is not simply copywriting transferred to a screen. A web writer must understand the reader's task, work with information architecture, structure pages for scanning, use links and headings well, and consider search terms and metadata. The writer may also examine usability sessions, edit existing material, and keep an inventory of what needs to be written. The book's distinction is practical: attractive sentences are not enough if visitors cannot locate information or complete an action. Writers should enter early enough to understand the project, not arrive at the end to replace placeholder text.
This broader role reflects how language shapes interface behavior. A label, error message, or instruction can determine whether a person succeeds, so writing belongs in design decisions rather than only in brand polish. Plain language also supports accessibility by reducing unnecessary interpretive effort. The expanded job description should not imply that one writer must master every discipline. Strong teams pair writing skill with research, design, and subject expertise instead of turning a versatile role into an excuse for understaffing.
Choose channels and tools after deciding what users need
Start with purpose, not platforms. A content management system stores and delivers material, but it cannot create a sound content plan or ensure that claims are accurate. Channel decisions should follow from audience needs, the kind of content required, available resources, and the work needed to maintain each channel. The same caution applies to social media. A forum does not create a community by itself: without a plan to attract participants, answer questions, and sustain activity, it can look abandoned. Before launching a channel, clarify why the organization is speaking, why it is listening, and who will keep the effort alive.
This argument anticipates a common technology mistake: buying capability before defining the work it must support. The same logic applies to AI publishing tools, recommendation systems, and social platforms. Automation can reduce repetitive effort, but it cannot settle what deserves publication or who is accountable when content misleads. Conversely, a tool can improve consistency when paired with sound governance. The important test is not whether a channel is fashionable, but whether its ongoing demands match the organization's capacity and users' expectations.
Measure behavior against business outcomes, not traffic alone
Set a baseline first. Web analytics can help teams understand how people encounter and use content, but useful measurement begins with defined objectives. The book points to measures such as reach, acquisition, conversion, and retention, then ties them to user tasks and business outcomes. Teams should record current performance and choose specific targets before changing content, so the effect can be assessed over time. A content evaluation can combine analytics with user research and audits. The Content Usefulness Toolkit, described as work by Content Delivery and Analysis, brings these sources together to assess whether content helps its intended audience.
Measurement makes content work legible to budget holders, but metrics are proxies, not verdicts. Page views may reward sensational material; clicks may rise even when people are confused and searching repeatedly. Pairing behavioral data with direct user feedback reduces that risk and helps explain why a number changes. Causal claims also require restraint: a conversion shift after a redesign may reflect seasonality, pricing, or promotion rather than content alone. Good measurement is a learning loop, not a scoreboard.
Appoint an editor with authority to retire stale content
Governance continues after launch. A content maintenance plan specifies what needs review, how often, who is responsible, and what standards apply. Maintenance can include checking accuracy, links, tone, metadata, and relevance, as well as archiving or removing outdated pages. The book distinguishes policies, which set mandatory constraints, from standards and guidelines, which establish consistent practices. It argues for an empowered web editor-in-chief who can set expectations, develop staff, coordinate with other groups, and say no when necessary. That role helps connect everyday publishing decisions to a broader web strategy rather than treating each project as a one-off.
Authority matters because distributed contribution without editorial accountability tends to produce inconsistent public information. Governance gives organizations a way to preserve institutional memory and correct errors even as staff and priorities change. The editor's power should be balanced by transparent criteria and routes for appeal, particularly when legal, commercial, and user interests conflict. The most sustainable model is not centralized control of every sentence, but clear ownership of standards, risk, and the decision to keep or retire content.
Analysis
The book's most durable contribution is its reframing of web content from a writing deliverable into an organizational operating problem. A page is not merely words placed inside a design. It has a source, a purpose, owners, review steps, technical dependencies, readers, and a future after publication. That systems view explains why last-minute writing fixes rarely solve content failures: the visible defect may be downstream of unclear authority, missing research, or an impossible schedule.
Its method is deliberately practical. Inventory reveals what exists; analysis distinguishes goals from requested tactics and tests assumptions; recommendations connect messages and user tasks to actual pages; workflow assigns work; measurement and maintenance keep the system accountable. This chain is valuable because each stage produces information needed by the next. Skipping analysis may feel faster, but it leaves decisions dependent on internal opinion and makes later changes more expensive.
The book also makes a persuasive organizational argument: better content requires authority, time, and sustained investment. Its limitation is that the detailed processes can appear heavier than necessary for small teams or low-risk content. The author's own advice to scale work rather than skip it points toward the right interpretation: preserve the questions and accountability, while reducing documentation to fit the stakes.
The environment described is centered on websites, CMS platforms, and early social channels. Today, content also travels through recommendation engines, messaging apps, and generative systems. Those channels increase the importance of provenance, review, and clear ownership, while automation makes sheer production volume easier. The book's warning against publishing simply because a tool makes it possible is therefore especially relevant. Its core test remains useful: can an organization explain who the content serves, what it helps them do, and who will care for it after release? If not, publishing more is unlikely to solve the problem.
Review Summary
Content Strategy for the Web receives mostly positive reviews for providing a comprehensive overview of content strategy fundamentals. Readers appreciate its practical approach, clear explanations, and useful frameworks for developing and implementing content strategies. Many find it helpful for beginners and professionals alike. Some criticize it for being outdated or too focused on large organizations. The book's emphasis on governance, auditing, and content lifecycle management is frequently praised. Overall, reviewers consider it an essential resource for those working with web content.
People Also Read
Glossary
Content strategy
Plan for content lifecycleThe practice of planning the creation, delivery, and governance of useful, usable content. It connects content decisions to business objectives and user needs, and addresses the people, processes, structures, channels, and ongoing care required to make content effective.
Content audit
Content inventory and evaluationA systematic examination of an organization's existing online content. A quantitative audit records what content exists and where it lives. A qualitative audit evaluates qualities such as accuracy, usefulness, relevance, readability, and audience fit. The results help teams scope, prioritize, and plan content work.
Strategic foundation
Agreed project contextA document that summarizes the findings of project analysis, including purpose, scope, business objectives, user needs, assumptions, success measures, and risks. It establishes a shared basis for decisions. It is not itself the content strategy, because it records context rather than recommendations for future content.
Content workflow
Steps and owners for publishingThe defined path content follows from request and sourcing through creation, review, approval, publication, and ongoing care. A workflow specifies tasks, responsible people, handoffs, timing, and notification or approval rules. It makes content production more predictable and clarifies where accountability sits.
Page table
Page-level content specificationA planning document describing the content needs of a particular page or component. It can record the page's purpose, key messages, source material, content requirements, and implications for creation, delivery, and maintenance. Page tables complement site maps and wireframes by specifying the content itself.
Content maintenance plan
Schedule for content upkeepA plan for keeping published content accurate, consistent, timely, and relevant. It identifies which content needs attention, what tasks are required, who is responsible, how long work may take, and which standards apply. It can also specify when material should be updated, archived, or removed.
Content Usefulness Toolkit (CUT)
Framework for evaluating usefulnessA toolkit attributed in the book to Content Delivery and Analysis. It combines a benchmark for what users find useful with content planning and audit methods, selected engagement metrics, and continuing user feedback. Its purpose is to assess whether content works for its audience and to identify where improvement is needed.
Top tasks
Users' most important actionsThe actions visitors most want to complete when they arrive at a website. Identifying these tasks helps teams prioritize content and functionality around real user goals, rather than internal preferences or an exhaustive list of organizational information.
FAQ
What's "Content Strategy for the Web" by Kristina Halvorson about?
- Introduction to Content Strategy: The book introduces the emerging practice of content strategy, focusing on planning for the creation, delivery, and governance of useful, usable content.
- Target Audience: It is aimed at companies, agencies, and beginning practitioners who want to understand what content strategy is, why it’s important, and how to implement it.
- Comprehensive Guide: The book provides a high-level overview of the benefits, roles, activities, and deliverables associated with content strategy.
Why should I read "Content Strategy for the Web"?
- Practical Insights: The book offers practical insights into how to fix web content and make it a valuable business asset rather than an afterthought.
- Strategic Approach: It emphasizes the importance of a strategic approach to content, which can lead to better user experiences and business outcomes.
- Expert Guidance: Written by Kristina Halvorson, a leading content strategist, the book is a trusted resource for anyone looking to improve their web content strategy.
What are the key takeaways of "Content Strategy for the Web"?
- Content as a Business Asset: Treat content as a critical business asset that requires strategic planning and ongoing governance.
- Comprehensive Process: Understand the full content lifecycle, from auditing and analysis to strategy, creation, and maintenance.
- Collaboration and Alignment: Emphasize the importance of collaboration across disciplines and alignment with business objectives and user needs.
How does Kristina Halvorson define content strategy in the book?
- Holistic Planning: Content strategy is defined as the practice of planning for the creation, delivery, and governance of useful, usable content.
- Beyond Tactics: It’s not just about tactics like blogs or social media; it’s a comprehensive plan that aligns with business goals and user needs.
- Content Lifecycle: The strategy covers the entire content lifecycle, ensuring content is treated as a valuable asset.
What are the main components of a content strategy according to the book?
- Creation: Determine what content will be created, why, and how it will be structured and sourced.
- Delivery: Plan how content will be delivered to users, including the tools and channels used.
- Governance: Establish who will maintain the content, how updates will be managed, and what standards will be enforced.
What is the role of a content strategist as described in "Content Strategy for the Web"?
- Content Advocate: The content strategist advocates for content throughout the project, ensuring it aligns with business and user needs.
- Research and Analysis: They conduct research and analysis to inform content recommendations and decisions.
- Implementation Oversight: The strategist oversees the implementation of content strategy, including creation, delivery, and governance.
How does the book suggest conducting a content audit?
- Content Inventory: Start with a content inventory, cataloging all existing content to understand what you have and where it lives.
- Quantitative and Qualitative Audits: Perform both quantitative audits (focusing on data and organization) and qualitative audits (focusing on content quality and effectiveness).
- Specialized Audits: Consider specialized audits for SEO, metadata, and localization to address specific content needs.
What is the importance of a content workflow as per the book?
- Streamlined Process: A content workflow defines how content is requested, created, reviewed, approved, and delivered, streamlining the process.
- Roles and Responsibilities: It clarifies roles and responsibilities, ensuring everyone knows their part in the content lifecycle.
- Efficiency and Quality: A well-designed workflow improves efficiency and content quality by preventing bottlenecks and ensuring consistency.
How does "Content Strategy for the Web" address content maintenance?
- Lifecycle Approach: The book emphasizes a lifecycle approach to content, where maintenance is an ongoing process, not a one-time task.
- Maintenance Plan: It suggests creating a maintenance plan that outlines tasks, roles, and schedules for keeping content accurate and relevant.
- Editorial Oversight: Regular audits and editorial oversight are crucial to maintaining content quality over time.
What are some of the best quotes from "Content Strategy for the Web" and what do they mean?
- "Content is the web.": This quote underscores the centrality of content in the online experience, highlighting its importance in web strategy.
- "Content strategy can help.": A simple yet powerful statement that encapsulates the book’s message that a strategic approach to content can solve many web-related challenges.
- "Content should be your first thought. Not an afterthought.": This emphasizes the need to prioritize content in web projects, rather than leaving it until the last minute.
How does the book suggest measuring the success of a content strategy?
- Web Analytics: Use web analytics to assess user behavior and measure the impact of content on business objectives.
- Success Metrics: Define clear success metrics tied to business goals and user needs to evaluate content effectiveness.
- Continuous Improvement: Implement a continuous improvement process, using data to make informed decisions about content updates and changes.
What is the relationship between content strategy and user experience design in the book?
- Interdependent Roles: The book argues that content strategy and user experience design are interdependent, with content being a key component of the user experience.
- Collaboration Needed: Successful web projects require collaboration between content strategists and UX designers to ensure content supports the overall user experience.
- Beyond Design: Content strategy goes beyond design, focusing on the substance and structure of content to meet user needs and business goals.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.