The Web3 Row on the Catalog, and What It Is Not

The shipped marketplace table has one row in Crypto & Web3. Code WEB3-105. Masked domain ending in chainwire.io. Title hint: Web3 infrastructure, DeFi, and crypto analytics. DR 62, DA 64, 51,000 monthly visits, DoFollow, turnaround 2 days, guest post $159, niche edit $129, spam score shown as 1%, top country US 38%, Google News marked yes, completion shown as 98%, sample path a /research/ slug. If the live table no longer contains that code, this paragraph is stale and the filter is the source. A campaign that needs ten crypto referring domains cannot be built from one code. Repeating the order ten times is still one referring domain.

US 38% is a fail for a product whose buyers are elsewhere, unless you write the reason. Google News on the drawer means the cell says yes. It does not mean your sponsored research note will be in a news carousel. Two-day TAT means the refund clock is short. Have the brief ready before you start it.

Read the middle row twice. 'Analytics' is doing a lot of work. A dashboard that shows fee revenue on a protocol can be a research piece. A page that tells the reader the token will go up cannot. If your only public page is a buy button, you do not have a research story, and the row will not manufacture one. Publish the methodology page first, the way the AI-search outline requires a definition before a mention.

The niche-edit price is $129. Ignore it until they send a /research/ URL that is indexed and already about reading on-chain data. A two-day turnaround is not a reason to skip that URL. Fast and unspecified is how you receive a sentence dropped into a price-prediction post. Reject that sentence the day it arrives. The refusal mail in the PBN worksheet is the right shape even when the defect is topic rather than template: name the URL, name the defect, ask for the refund.

TECH-107 is general news at $349 and DR 76. It is not a backup crypto row for a product the FAQ would refuse, and it is not a backup for a product that simply failed the research test. A startup-news site can cover a company that builds infrastructure. It should not cover a token sale because WEB3-105 was full. MKT-106, the indie-hacker blog, is the same trap at $99. If the only keeps on your gap sheet are 'crypto' and the catalog has one code, the campaign is one order or it waits. Write 'wait' in the plan. A plan that quietly becomes four general-news posts is a different plan, and the safety note should say so.

TAT is 2 days, so the refund mail is due on day 4 if there is no URL, not at the end of the week. When the URL arrives, check the path. You asked for a research-shaped piece. If the live URL is a price-prediction slug, or the paragraph tells the reader what to buy, reject it even if the anchor is the product name. The sample path in the catalog is /research/. A URL that is not in that family needs an explanation before you accept it.

Also search the page for the token ticker and for the words 'guaranteed' and 'return.' Those words are a fail even on an infrastructure company, because the article has changed the subject. Reply with the URL and the sentence. Ask for a takedown or a refund. Do not let a two-day turnaround become a reason you 'don't want to make a fuss.' Fast delivery of the wrong page is still the wrong page.