The Name Retailer guide library
Practical guides for your next move.
Explore our SEO, AEO, GEO, content, marketplace and measurement articles. Find clear answers, worked examples and practical checklists—all in one library.

GEO
01Choose one content improvement, define what you will observe and decide when to review the result before starting. Keep the experiment small enough to explain its limitations. The objective can include clearer answers and better reader outcomes even when generative-search appearances are sparse or variable.
Read the guide ↗Technical SEO
02Separate migration decisions into content equivalence, URL mapping, metadata, media and release behavior. A new interface is not a complete migration if valuable old pages and destinations remain unaccounted for. Review the old inventory before switching hosts or enabling redirects.
Read the guide ↗Measurement
03Inspect a backlink export's source, collection date, URL fields and link attributes before drawing conclusions. The analyzer can count rows and referring domains, but those counts inherit the report's coverage and freshness. They do not establish that every link is still live or relevant.
Read the guide ↗Technical SEO
04Choose the intended public URL for each article and make its canonical metadata consistent with that destination. A canonical identifies the preferred equivalent version; it is not a shortcut for merging unrelated pages. Review URL choices before migration rather than relying on whatever route happens to render first.
Read the guide ↗GEO
05Write factual claims so the reader can distinguish the supported statement from your interpretation. Link to the exact document that supplies the fact, then label any recommendation as your own guidance. Citation-friendly writing is a clarity practice, not a promise that an AI system will cite the page.
Read the guide ↗Measurement
06Record the page change, timing, measurement window and other events that might influence the outcome. An experiment log should make alternative explanations visible. This is especially important when content edits happen alongside product launches, advertising or a website migration.
Read the guide ↗Content
07Refresh an article when its answer, evidence or practical instructions need a substantive change. Keep a short log of what changed and why. Updating a date alone does not tell the reader that the guidance was actually reviewed or improved.
Read the guide ↗GEO
08Use consistent criteria, dated evidence and explicit unknowns when comparing options. Explain the perspective of the publishing brand rather than implying independent neutrality. A fair comparison can describe trade-offs without inventing competitor weaknesses or declaring a winner from incomplete information.
Read the guide ↗Measurement
09Define the business question, metric and observation source before publishing a campaign report. Separate discovery, visits and completed actions so the report does not imply that they are interchangeable. A measurement plan should also specify unavailable data and the limits of attribution.
Read the guide ↗Marketplace
10Build a placement budget from separate cost lines: publication, article preparation, revisions and any agreed fees. Compare complete quotes in the same currency. A low headline placement price is not necessarily a low total project cost when the writing and editorial scope differ.
Read the guide ↗Measurement
11Track actual referred visits separately from publication-wide traffic estimates. Record the article or referring domain, reporting period and the measurement source. A placement's presence on a site does not establish how many readers clicked through or what they did after arriving.
Read the guide ↗Technical SEO
12Check an article at narrow mobile, tablet and desktop widths with the same content and interactions. Readability depends on line length, spacing, headings and working controls, not just a lack of horizontal scrolling. Test the sidebar and tables with real long titles rather than a short sample.
Read the guide ↗Content
13Keep a source log that connects each checkable claim to the exact supporting page, observation date and any relevant limitations. This makes review easier than a general bibliography with no claim mapping. Prefer first-hand documents when the article explains a product, policy or technical behavior.
Read the guide ↗Technical SEO
14Make structured data describe the article readers can actually see. Use the real title, actual publication history and legitimate author entity. Validate syntax and inspect the rendered page together; passing a JSON parser does not establish that the markup is accurate or eligible for a search feature.
Read the guide ↗AEO
15Treat answer clarity, factual review and indexing approval as separate gates. A well-structured preview article can be ready for owner review while still intentionally excluded from search. Do not remove launch protections merely because headings, metadata and direct answers have been added.
Read the guide ↗GEO
16Decide crawler access from the product and purpose you actually intend to support. Search discovery, assistant retrieval and model-training controls are not necessarily the same. Review each relevant provider's current documentation rather than applying a universal 'AI access' rule inferred from a tool name.
Read the guide ↗AEO
17Review an answer by asking whether it is correct, understandable, sufficiently complete and useful for the stated reader. Use concrete notes rather than a mysterious aggregate quality score. A review sheet should identify the revision needed and the evidence that would close each issue.
Read the guide ↗Content
18Before publication, hand over a complete package: approved text, checked sources, usable media, metadata and clear unresolved questions. The receiving editor should not have to infer permissions, authorship or commercial link treatment from scattered messages. A clean handoff makes responsibility visible.
Read the guide ↗Marketplace
19Review a sample of articles for usefulness, attribution, consistency and topical relevance. Keep concrete observations alongside the shortlist so another person can understand the decision. This is an editorial assessment, not a certification or a proprietary score calculated from a few visible pages.
Read the guide ↗AEO
20Group related questions by the decisions they support, then assign one useful page to each distinct task. A question map should expose gaps and duplication, not become a mandate to publish every wording variation. Start with a manageable set grounded in the reader's workflow.
Read the guide ↗GEO
21Inventory the evidence a brand actually possesses before writing claims about clients, outcomes or verification. Record permission, source and scope beside each item. An attractive design reference can show how evidence might be displayed, but it cannot supply the underlying business facts.
Read the guide ↗Measurement
22Report the starting value, ending value, period and calculation alongside a percentage change. A large percentage can come from a very small baseline, and a zero baseline needs special handling. The number should help the reader understand the observation rather than make a chart look dramatic.
Read the guide ↗Technical SEO
23Inspect the HTML returned for an article as well as the hydrated browser page. The title, main answer and navigation should be available in a stable, understandable form. A route that looks correct only after a client-side request needs a separate discovery and failure-state review.
Read the guide ↗Measurement
24Select a reporting window that fits the question, and disclose why that period is useful. Keep comparison periods consistent and note material differences. A narrow favorable window can make ordinary variation look like a durable improvement, especially when the underlying counts are small.
Read the guide ↗Examples are illustrative unless an actual source is identified.