Check the task, step by step.
Practical guides for spreadsheet imports, campaign links and website handovers. Each one includes a concrete example and a tool you can try.
Compare an approved offer with every final email variant
Duplicating a promotional email is useful until one country or client variant keeps the old discount, coupon or button destination. Valid UTM parameters cannot establish which offer the client approved. Use the approved campaign sheet as the comparison source.
Check an approved promotion against exported Klaviyo email HTML
Use a final template export for a local offer comparison. A screenshot can show a correct-looking button while hiding its actual href. An HTML export lets you compare the supplied text and destination before the send-time changes happen.
Check client newsletter links against the intended domain and campaign
Before asking a client to approve a newsletter, check the destination list against the client host and the specific campaign you meant to send. A link can contain complete, lowercase UTM tags and still belong to another client or last month’s campaign.
Preserve leading zeros when copying a web table
An order code such as 001027 is an identifier, even though it contains only digits. If a spreadsheet imports it as a number, it can become 1027. Changing the cell’s format afterward cannot recover the original zeros unless you already know the correct length.
Avoid rounding long reference numbers in spreadsheets
A reference number can be longer than the precise numeric range a spreadsheet supports. If the application interprets it as a number, two different references can become the same rounded value. A displayed value that looks plausible is not enough evidence that the identifier survived.
Convert DD/MM/YYYY CSV dates without guessing
03/04/2026 can mean 3 April or 4 March. Neither interpretation can be determined from that cell alone. A date conversion tool should ask for the source format rather than guess from your browser or computer locale.
Find duplicate UTM parameters before sending a campaign
A URL can contain utm_campaign twice. One analytics system may use the first value while another uses the last. That inconsistency makes a campaign’s destination harder to interpret even when the page loads successfully.
Validate a campaign destination against the intended domain
A campaign can have correct UTM fields and still point to the wrong website. A staging domain, a misspelled host or an unexpected subdomain can survive a quick visual review. Checking the parsed hostname gives you a precise rule to apply to every link.
Make a practical UTM naming convention checklist
A naming convention is useful only if people can apply it consistently to the final links. Newsletter and newsletter can create different values; spaces can introduce yet another variation. A short, explicit rule set makes those differences visible.
Create a website launch handover checklist with evidence
A handover checklist should tell the next person what was observed and what still needs verification. A single score can hide that distinction. A page report with a capture time and a concrete reason for each result makes the scope easier to review.
Check rendered noindex before a website launch
A staging site may deliberately include a noindex directive. If that directive survives the launch, it deserves investigation. Checking the rendered robots meta is a useful first step, but it covers only one place where indexing instructions can exist.
Prepare a client website handover report without overclaiming
A useful client report does not need an inflated readiness score. It needs a clear page identity, a capture date, understandable findings and a list of work outside the test’s scope. That makes it easier for the recipient to decide what to verify next.