An old AIP recipe that still calls for eggs can cause real confusion for someone in the elimination phase. Before changing the headline or adding photos, check the ingredients and say plainly which phase the recipe suits. That focused correction can make an older page useful again; it doesn’t need a full rewrite.
Choose pages with a reason to update
Make a short inventory of older pages. For each one, note its original purpose, last substantial review, current usefulness, and any claims that depend on changing evidence or product availability. Age alone is no reason to revise a sound explanation of food diaries. But a recipe with unavailable ingredients, broken instructions, or an unclear AIP label needs attention, even if it’s relatively new.
Start with errors that could affect food choices. A post about elimination and reintroduction needs a closer review than a seasonal roundup of lunches. Comments and messages can point you toward trouble spots, though one reader’s question doesn’t speak for everyone. Repeated questions about nightshades, for instance, may tell you the recipe needs an ingredient note.
- Keep and revise: The topic is still useful, but the details, examples, or instructions have aged.
- Combine: Two short pages answer nearly the same question and would be clearer together.
- Retire or redirect: A page no longer has a distinct purpose. Give visitors a route to relevant information rather than a dead end.
For a small site, a spreadsheet with the page address, problem, proposed fix, reviewer, and completion date is enough. It shows which pages were actually checked, rather than merely given a new date.
Check the practical details first
Read each page as though you’re about to use it. In a recipe, compare the ingredient list with the method, servings, cooking time, storage advice, and dietary labels. If the marinade lists coconut aminos but the method never mentions them, fix that before polishing the introduction. If the recipe is called “AIP-friendly,” specify whether that means the elimination phase or a later phase after a particular food has been reintroduced. Suitability depends on the person and the phase; a broad label can’t decide it for everyone.
Planning posts need the same practical test. Does a seven-day menu stretch one batch of leftovers too far, lack variety, or assume access to costly specialty foods? Where possible, offer workable alternatives instead of rigid rules: a cooked vegetable might replace a raw one, and a shopping list can group protein options rather than require one specific cut.
Separate evidence from experience
Nutrition and digestive-health posts often age because their claims sound more certain than the evidence allows. Revisit lines such as “this food heals the gut” or “bloating means a particular intolerance.” Symptoms have many possible causes, and microbiome research doesn’t show that everyone responds the same way to one ingredient. State only what the evidence supports, and distinguish a practical experiment from a proven treatment.
Check the context of any research you cite. Was the finding drawn from a small study, an animal experiment, or an observational report? Has the post turned a possible association into advice for everyone? Readers don’t need a technical review in every article, but they should be able to see what’s known, what’s uncertain, and where the limits of the advice lie.
A food diary can show how someone noticed a pattern; it can’t diagnose a sensitivity. Diary guidance can suggest recording approximate portions, timing, symptoms, sleep, and other circumstances. It should not encourage readers to cut more foods after one uncomfortable day. Recommend discussing persistent symptoms and planned dietary changes with a doctor. Elimination diets are not a substitute for medical care.
Improve the path through the page
Make the answer easy to find
Older posts sometimes bury the part readers came for. Put the key distinction or first workable step near the top, while keeping the context needed to use it safely. Define the phase before listing foods in a reintroduction post. In a recipe, place the yield, preparation time, and substitutions where a cook can find them before shopping.
Choose headings that tell readers what’s in a section rather than promising a dramatic result. Split a paragraph when it covers separate actions, but don’t make every sentence a bullet. A table may help compare parallel checks for a recipe and an educational post; a point that needs nuance is usually better explained in prose.
Check links, images, and labels
Open every link to make sure its destination still supports the surrounding sentence. Remove one that now leads somewhere unrelated. If another post on your site supplies needed background, link to it in a descriptive sentence—not just to increase the link count. Check that image alt text describes the image that’s actually there and that diagram text is legible on a phone.
Give dietary labels a separate pass. “Paleo,” “grain-free,” and “AIP elimination” do not mean the same thing. A dessert made with almond flour may suit some paleo-style eating patterns but not an AIP elimination menu. Update both the category and the page copy so they don’t give conflicting guidance.
Publish the revision honestly
Keep the original publication date if your site displays it. Add an updated date when substantial information has changed, not for a spelling fix. For an important correction, a short editor’s note can explain what changed—say, the recipe’s AIP phase label and substitution advice. If the topic is unchanged, keep the page address so existing bookmarks work.
Preview the page on a narrow screen before publishing, then follow the instructions once more. Do the ingredients match the steps? Are the headings in a sensible order? Does a note at the end contradict the label near the top? After the update goes live, check recurring questions and comments to see whether readers are still confused.
For a first pass, pick one older recipe and check its dietary label, ingredient-to-method match, and storage instructions. Correct what you find and log the review date. That gives you a dependable starting point for the next page.
