About the publication
Our editorial lens
What this site covers, what it deliberately leaves out, and how a case study earns a place here.
What does this site actually cover?
Tuwopa Yaxaxa exists for a narrow slice of a much bigger topic. Not marketing, not branding, not conversion copywriting. Just the technical mechanics of what happens to a website's relationship with search engines when the site itself changes shape: a new domain, a new CMS, a folder structure rebuilt from scratch, or a full redesign that quietly renames every page.
Articles here tend to sit in three neighborhoods. Redirect logic and URL mapping. Staging, testing, and pre-launch quality checks. Rank and traffic monitoring using tools that do not require a subscription. A fourth, smaller neighborhood holds post-mortems, dissections of migrations that were publicly documented somewhere else first.
Why doesn't this site offer migration services?
Because the moment a publication starts selling the thing it writes about, its judgment becomes hard to trust, including its own. Every article on this site is written as though the author has no stake in whether a reader hires anyone at all. There is no consulting arm, no audit product, and no affiliate relationship with migration tools mentioned in these articles.
Readers looking for hands-on help with an actual migration are better served finding a developer, agency, or in-house engineer directly. This site is a reference, not a service directory.
How a case study earns its place here
It has to be public
Only material already shared publicly, in a blog post, forum thread, conference talk, or documented case write-up, is used as a source. Nothing from private client work appears here.
The timeline gets checked
Dates matter. A traffic drop reported "after the redesign" needs a redesign date and a drop date that plausibly line up, ideally corroborated by more than one source.
Causation is treated carefully
A drop that followed a migration is not automatically a drop because of the migration. Where the original source hedges, this site hedges too.
No numbers get invented
If a source does not include a figure, this site does not supply one. Vague language, "a noticeable decline," is used honestly rather than replaced with a made-up percentage.
Who reads a draft before it publishes?
Every article passes through a second technical read before it goes live. That reviewer is asked to check three things and only three: is the terminology correct, is the recommendation reasonable rather than absolute, and does every named source actually say what the article claims it says.
Corrections are made in place when an error is found after publication, with a short note added at the bottom of the article describing what changed. Nothing gets quietly rewritten.
Content on this site reflects publicly available information current as of its publication date and may not reflect later changes to the tools or platforms it describes.