A tutorial says “cut two 4-inch panels” but never gives the card-base size. A supply review praises a marker you no longer use. A holiday card’s photos show the steps in a different order from the instructions. Those are the kinds of problems worth catching before a website update makes them harder to spot.
For a cardmaking blog, a content audit means checking whether each page delivers what it promises and whether its instructions and materials still hold up. Then you decide what to keep, correct, update, combine, or remove. You do not need to rewrite the whole archive at once. A small inventory with clear notes is far more useful than a rushed overhaul.
Set the boundaries before opening old posts
Start with the website change you are planning. A new design may affect captions, step numbers, and wide process photos. A new tutorial format may expose missing measurements. A navigation update may bring several near-identical beginner guides together. Write down which pages the change touches so you know where to start.
For a manageable first pass, include:
- Posts featured in navigation, category pages, or prominent links.
- Tutorials readers still visit, save, or ask questions about.
- Posts in an older format that the new design may display differently.
- Seasonal projects that need checking before their next useful season.
- Supply reviews and technique guides whose products or instructions may have changed.
Put everything else in a separate “later” group. An archive-wide audit may be worthwhile, but it should not hold up a specific site update while you polish every old birthday-card post.
Make an inventory you can actually use
Use a spreadsheet or simple document with one row per page. Record the title, current address, content type, date last meaningfully checked, primary reader task, and whether the page is in scope. Add columns for issues, decision, priority, owner if you work with others, and status. A final “checked on” date distinguishes a completed review from a page you merely opened.
The reader task is particularly helpful for craft posts. “Make a heat-embossed greeting without scorching the cardstock” tells you more than “embossing post.” It gives you a way to judge the instructions, photos, and troubleshooting advice.
Do not treat publication date as proof that something is wrong. A well-photographed paper-folding technique may still be accurate years later, while a newer lighting tutorial could name the wrong battery type. Dates tell you what to inspect, not what to delete.
Review each page as a maker, not just an editor
Open the published page first, ideally on both a phone and a larger screen. Read it in the order someone making the card would. If you still have the sample or project notes, compare them with the instructions. You do not have to remake every card, but verify measurements and tricky steps rather than guessing.
Check the project promise and practical details
Does the opening show the finished result and make clear what the reader will learn? A title promising a pop-up card should not lead to a flat layered card with a pop-up variation tucked at the end. Check finished dimensions, cardstock weights where they matter, quantities, cutting measurements, and wait times for ink, paint, or adhesive.
Pay particular attention to mistakes a reader cannot easily undo: folding direction, die placement, stamping order, and which side of a panel gets adhesive. For a light-up card, verify component orientation and how the circuit is activated. Make sure the instructions say to keep small batteries away from children and pets. If you cannot confirm an electrical detail, flag it for a fresh build rather than repeating the old wording.
Check materials without confusing a product with a technique
An unavailable stamp does not automatically make a tutorial obsolete. If any similarly sized outline stamp will work, describe that requirement in the materials list and keep the original product name only if it adds useful context. If a particular die creates the mechanism, say so; do not suggest an untested substitute is equivalent.
Reviews call for a different approach. Keep the date and scope of your original hands-on experience clear. Correct factual mistakes and broken claims, but do not quietly rewrite an old assessment as if you tested a newer product version. Add a dated note if the material has changed or later experience substantially qualifies your review.
Check photos, text, and page behavior together
Each photo should match the step it supports. A close-up of a finished bow cannot show someone how to thread the ribbon. Check whether images are sharp enough to show alignment, whether captions point out what matters, and whether step references still work when photos move in the new template. Alt text should describe useful visual information, not repeat a decorative caption or claim to show a process that is not visible.
Test downloads, embedded content, forms, and links. A printable template at the wrong scale can spoil an otherwise sound tutorial. If a linked supply is unavailable, decide whether to remove the link, use a general material description, or offer an alternative you have tested. The aim is to help someone finish the card, not just clear an error report.
Use evidence, but do not let one number decide
Analytics can help you choose what to check first. Visits, search queries, and recurring entry pages may show where outdated instructions affect the most people. Comments and reader emails reveal another kind of urgency: even a low-traffic tutorial can contain a measurement error that wastes cardstock. Site searches may point to a technique readers expect to find but cannot locate in an existing post.
If you are deciding which figures matter, website analytics metrics for cardmaking blogs explains them in more detail. For this audit, record only evidence that helps you make a decision. “Several readers asked where to attach the foam tape” is more useful than an unexplained column of numbers.
A quiet page is not necessarily useless; a niche stencil technique may serve a small group very well. A popular page, meanwhile, may need immediate correction if its instructions are confusing or unsafe. Traffic tells you about reach, not craft accuracy.
Choose one outcome for each page
Give each page a decision label so the inventory does not become a collection of vague notes. Then describe the actual work in the issues column.
| Decision | Use it when | Example action |
|---|---|---|
| Keep | The page still fulfills its promise and works in the planned layout. | Record the review date; skip cosmetic rewrites. |
| Correct | A limited, verifiable error or broken element needs repair. | Fix a panel measurement and check every later reference to it. |
| Update | The project remains useful, but substantial guidance or photos need work. | Retest a marker-blending method and replace unclear process images. |
| Combine | Two pages answer essentially the same reader task, and each has useful parts. | Build one complete guide and decide what to do with the retired page. |
| Retire | The content cannot be verified, no longer serves its promise, or would mislead readers. | Remove it after checking relevant references and destinations. |
Combining or retiring a page takes more planning than fixing a paragraph. Check whether other posts, saved reader references, downloads, or navigation items point to it. If you change its address, redirect it to a genuinely relevant surviving page when one exists; do not send every retired tutorial to the home page. If there is no suitable replacement, consider whether a clear notice or a normal not-found page would better serve visitors. Record the old address and what you chose to do with it.
Before combining projects, make sure they solve the same problem. A beginner guide to using a stencil and an advanced layered-stencil card may use the same tools but serve different readers. Joining them could make both harder to follow.
Prioritize fixes that protect the project
Give each page a priority: urgent, next, or later. Incorrect measurements, misleading safety details, missing templates, and broken essential steps belong in the urgent group. Next come pages central to the planned site change or explanations that repeatedly prompt reader questions. Save cosmetic improvements and functional posts for later.
That order keeps you from spending an afternoon replacing a slightly dated hero photo while a popular folding tutorial still has an impossible cut size. Estimate effort separately from priority: a five-minute correction and a full project reshoot may both be urgent, but they need different slots in your schedule.
For an edit larger than a factual fix, add a short brief to the inventory. Note what needs testing, what you can reuse, which photos are missing, and what a reader should be able to do when the page is finished. It helps keep the tutorial’s scope from drifting mid-edit.
Handle corrections and updates transparently
A silent typo fix rarely needs a note. A corrected measurement, changed circuit diagram, or revised product assessment might affect someone who saved the earlier version. In those cases, add a short dated correction or update note explaining what changed. It need not become an editing diary.
Keep what already works. If a heat-embossing guide has accurate steps and helpful photos but an outdated supply list, fix the list and leave the instructions alone. If you make a new sample card, label old and new photos clearly instead of mixing two builds into what looks like one sequence.
After a substantial update, test the published page the way a reader would: find it through its usual category, follow the steps, open the printable, and check it on a phone. If new images slow the page down, improve how they are delivered without removing close-ups that show the technique. The guide to speeding up cardmaking tutorials without losing photo detail
Keep a record that makes the next audit easier
After each update, note what you verified, what changed, and what remains untested. “Checked finished width against sample; corrected step 4; template opens at intended scale” will help the next time you revisit the page. “Updated” will not. If you could not recreate a technique that relies on a discontinued product, record that limitation rather than leaving a future editor to assume you tested it.
Use triggers for future reviews instead of repeatedly checking every post on a fixed schedule. A reader-reported error, a changed product, a redesign that affects image display, or an approaching seasonal window can each prompt a targeted check.
For your first pass, pick five posts the website update will touch. Give each a reader task, a decision label, and one next action. “Birthday shaker card: update; retest foam-tape placement before replacing step 6 photo” is enough to put that page in a practical editing queue.