Start with the domain you control. ReviewList saves your claim while you add a unique DNS record, then opens your business workspace after ownership verification.
Choose the domain your business controls
Enter your public store domain in the business setup form, then create an account or sign in. Check the spelling: a similar-looking domain belongs to a different profile. Use a customer-facing domain you manage, rather than a checkout URL or social account.
Selling through a hosted storefront does not automatically give you control of the hosting platform’s domain. If your store only uses a shared hosted subdomain, do not assume you can verify it. Ask whoever manages your custom domain to help with DNS, or obtain a domain you control before attempting ownership verification.
Copy the record from your saved claim
Your workspace shows a TXT record with the host _reviewlist and a unique value for your claim. The full record name is _reviewlist followed by your store domain. Copy the displayed value exactly; the example name is not a reusable verification token. Add the record in the DNS service currently responsible for the domain.
Some providers append the domain to a short host name; others require the full name. Check the field description to avoid creating _reviewlist.yourstore.com.yourstore.com accidentally. Use the default TTL and keep existing website and email records in place.
Return to verify, or resume after propagation
Save the DNS change and use Verify store ownership in ReviewList. If the record is not found, compare its name, type, and value with the saved claim before retrying. DNS changes may take time to become visible. The claim remains saved, so you can return using the same account instead of creating repeated setup requests.
Your public profile and customer review link can be available while verification is pending. Profile management, campaigns, widgets, and business replies require the verified workspace. If the profile is already claimed by another owner, resolve that ownership with the current owner or an administrator; publishing a competing token is not an ownership-transfer process.
Check what verification actually means
A DNS check establishes domain control, not product quality, every customer purchase, or search visibility. Keep public details accurate and use your customer link to collect real experiences. Domain ownership and business-identity verification are distinct observations.
After setup, check that you are managing the intended store. Free includes profiles, replies, widgets, and invitations; paid checkout is unavailable. Claiming a profile or paying never changes moderation decisions or buys a better rating.
Ownership setup check
| Check | What to confirm |
|---|---|
| Store domain | The public custom domain is spelled correctly and you control its DNS. |
| Record type | TXT, with the exact unique value from your saved claim. |
| Record name | _reviewlist, or the full name if your provider requires it. |
| Existing records | Website and email records remain in place. |
| Workspace | Verification completes for the intended store and account. |
Questions and answers
Do I need to change nameservers?
The ReviewList claim requires a TXT record in your active DNS service. It does not require changing nameservers. Confirm where your domain’s DNS is managed before adding the record.
Can I verify a store on a shared hosted subdomain?
Only if you can publish the required record at the exact domain being claimed. A storefront login alone does not establish DNS control. Use a custom domain you manage.
Does a claimed profile guarantee search visibility?
No. Ownership and search eligibility are separate. A profile can stay accessible while ReviewList builds the eligible review coverage and useful evidence needed for indexing.
Sources and scope
ReviewList publishes this guide to explain a practical research or review workflow. Linked sources support the specific external principles discussed; they are not endorsements of ReviewList. Current merchant terms and the details of a particular order may differ.
Editorial date: Oct 13, 2026. Suggest a factual correction.