π Why site metrics can look different
Search Atlas shows publisher-site Domain Authority from vendor data, not from its own scoring system. It uses the SEMrush authority score when that score is present and above zero, and falls back to the stored Moz Domain Authority otherwise. A site can show a higher DA in another tool because that tool uses a different measurement. The difference does not mean the platform number was copied incorrectly from that outside score.\n\n
Organic Traffic is also taken from vendor data, not calculated by Search Atlas. The platform uses SEMrush organic traffic first, then its stored SEMrush-verified traffic, and finally the older Ahrefs traffic figure if neither SEMrush value is available. If the number does not match an external report, compare the two as separate measurements rather than treating the platform value as a failed copy.\n\n
π‘ How pricing and site activity affect eligibility
A site must meet the platformβs requirements for the price you set, including the Domain Authority price cap. A price above that cap is rejected. An inactive status is separate: a site can be inactive because the publisher was deactivated, its metrics fell below a threshold, or for another recorded reason. If a listing looks under-qualified despite a high external DA score, check both the siteβs status and whether its price meets the platformβs requirements.
- The platform does not rely on DA alone.
- An inactive site is not eligible while it remains inactive. Inactivity can result from publisher deactivation, metrics below a threshold, or another recorded reason. It does not by itself mean the price you set was rejected.
- Adjust expectations for eligibility based on the platformβs own result, not only an outside DA score.
π οΈ Meta tag verification and sync
A failed meta tag check can be caused by the wrong UUID in the tag. After you correct the tag on the site, run verification again. The platform checks the live page immediately. There is no separate sync to wait for. Passing the meta tag check proves ownership, but the site still has to pass the platformβs other approval checks before it goes live.
π What to expect for low orders
Low order volume is not always a calculation error. Orders depend on customer demand and whether the site is eligible and visible in the marketplace. There is no rule that orders will still arrive through the end of the current week, so waiting until then does not show whether the order count is wrong.
β What you can check yourself
- Treat platform Domain Authority and Organic Traffic as vendor readings selected by the platform, not as a Search Atlas calculation and not as a mirror of every third-party report. Another tool can show a different number because it uses a different measurement.
- Confirm the site is active and that its price fits the platformβs requirements.
- If meta tag verification failed because of a wrong UUID, correct the tag and run verification again. The platform checks the live page at that time. There is no record sync to wait for. Ownership verification can then succeed, but the site goes live only if it also passes the platformβs other approval checks.
- If orders are low, wait until the end of this week before escalating the same concern again.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.