This methodology describes how XrdaGrid converts marketplace and regulatory information into practical guides, comparisons, and decision routes.
1. Define the page scope
Each page is assigned a primary topic, intended audience, jurisdiction, marketplace, product context, canonical URL, parent hub, search intent, and internal-link plan before research begins.
2. Build the evidence record
- Official marketplace documentation and seller guidance
- Laws, regulator guidance, fee schedules, and government publications
- Official provider documentation, checkout pages, and written quotations actually obtained
- Reliable secondary sources used only for context or discovery
Material claims are tied to sources in a research pack or evidence library entry. Sources are recorded with the access date and the scope they support.
3. Separate different types of requirements
A marketplace policy is not automatically a legal requirement, a law may not apply to every product or seller, and a provider statement is not independent proof. We identify the authority, jurisdiction, conditions, and known limitations. Where the evidence is incomplete or conflicting, we say so instead of inventing certainty.
4. Identify the practical routes
We first check whether a seller can use an existing manufacturer document, an official government route, or a reasonable do-it-yourself process. Paid software or service options are presented when they solve a distinct need, not as the automatic first answer.
5. Evaluate providers
Depending on the comparison, criteria may include service scope, eligibility, jurisdiction coverage, required inputs, turnaround claims, support, pricing transparency, deliverables, revision or update policies, cancellation or refund terms, and documented limitations. Provider inclusion is not an endorsement or proof of partnership.
6. Check mutable facts
Prices, marketplace policies, program terms, product features, and other changing facts receive an “as of” date and are rechecked before publication or a material update. Our separate price-verification policy explains how fees are reported.
7. Run editorial and publication QA
Every page is checked for unsupported claims, source quality, jurisdiction, dates, link integrity, affiliate disclosure, metadata, schema, accessibility, mobile presentation, and consistency with the current WordPress build. See the Editorial Policy.
Corrections
Material corrections are reviewed against evidence. The last-reviewed date is updated when a page receives a substantive verification. Report an issue through the Contact page.