A Foreign-Trade Standalone Site With No Inquiries for a Year: A Diagnostic Path From Indexing to the Form

When a foreign-trade standalone site has been live for a year with zero inquiries, the owner’s first reaction is usually that Google has banned it. We took our own site apart layer by layer: 100% indexed, 0 clicks and 12 impressions over the past 28 days. What’s stuck is neither indexing nor the form.

With no inquiries for a year, what order should you check things in?

An inquiry is the last cell of the funnel; if any earlier cell is broken, the last one will never show a number. So a diagnosis should not begin with “is the form broken?” — it should start at the very top and work downstream.

The order we use has six layers, and each layer answers exactly one question. If the previous layer’s answer is uncertain, the next layer’s conclusion does not hold. That is the premise that makes the whole path work.

The most important thing about this table is not the numbers, it is the order. The mistake owners make most often is skipping the first few layers and jumping straight into “should we redesign the page?” — but a redesign cannot fix indexing or impressions.

One more rule to set in advance: for every layer, write down what data would overturn it. A judgement with no falsification condition is just a guess, and a guessed conclusion will not change the site.

Write the six layers down on paper and record the result and the date after each one. The benefit is very practical: two weeks later you can tell whether you are actually making progress or just repeating the same guess in place.

Is indexing actually the bottleneck?

What we found on our own site

On the indexing layer, in the GSC diagnostic dated 2026-10-02, this site’s indexation rate is 100% (10/10). Every newly published page entered the index; there was no case of “dozens published, not one indexed.”

In other words, the guesses about “the site was penalized by Google and none of the content gets indexed” do not hold for our site. It proves at least one thing: the publishing channel works.

How to confirm whether a page is actually indexed

In practice it is simple: put the target URL into Search Console’s URL Inspection and see whether it comes back as indexed or not indexed. Do not just look at the number of URLs submitted in the sitemap — submitted does not equal indexed.

On this site, all 10 of 10 pages were indexed. Read the other way, that number also says the problem is not technical indexing but whether the content connects with demand.

What 100% indexing actually tells you

Indexing only settles “is the page eligible to be found in search.” It does not settle “does anyone search, where do you rank, did anyone click.” Treating indexing as the whole of SEO is the first misunderstanding this diagnosis has to dismantle.

Judging indexing always has to come down to a specific URL. A site-wide indexed count is meaningless; that number pulls in irrelevant pages and actually leads you to believe indexing is fine.

When fixing indexing should come first

If in Search Console the target page sits at “Discovered — currently not indexed” for a long time, then stop there and fix indexing first. In that case there is no point checking the next five layers; checking them is wasted effort.

That was not our case this time, so the problem moves to the next layer. We recorded the full procedure for this step in the research notes index, alongside the hands-on tests from other rounds.

What does it mean when indexing is fine but there are no impressions?

Impressions are the number of times a page has been shown in search results. Indexed but with very few impressions means it matched very little search demand, or it did match but you rank so far down that you never entered the visible area at all.

This site had 12 impressions over the past 28 days. That number is too small to show a trend, but it is enough to show one thing: almost no demand is coming in. So the problem is not “the page is not indexed” but “no demand is finding its way in.”

The cause usually falls in one of three directions. The keywords are too narrow, or they are words your competitors search rather than buyers; the content is too thin to carry a topic; or the site’s positioning simply does not chase this volume.

Demand can only be judged from search data, not from feeling. A word being said every day in your industry does not mean it has ever been typed into a search box.

Thin content is a different matter. Thin does not mean few words; it means the content did not finish answering a complete question. A reader arrives with a question, finishes the page, and the question is still there — that page is thin.

The third one has to be faced honestly. tianwenseo.com is positioned as a research notebook plus a test field, not a main traffic site. Asking “why are there no inquiries” under that positioning has part of its answer written into the positioning from the start.

There is a misjudgement to avoid here: do not infer “we were demoted” from “no impressions.” A demotion is a conclusion that needs evidence, and zero impressions should first raise suspicion about demand volume and content depth, not about a penalty.

When looking at impression trends, fix the observation window — read 28 days at a time, do not refresh every day. When the data volume is small, all the movement on a daily line chart is noise. This habit follows the same logic as the fixed panel we use for AI visibility monitoring.

With impressions but no clicks, which layer is stuck?

Clicks are downstream of impressions. This site had 0 clicks over the past 28 days, but only 12 impressions, so this pair of numbers cannot be used to judge whether the titles are well written.

Between 0 clicks on 12 impressions and “the titles are bad” sits an enormous sample-size problem. We have a hard rule when running AI citation monitoring: when a cell has only 3 samples, the difference between rounds contains sampling noise and is not used to draw causal conclusions. The same discipline applies to click-through rate.

Search intent can be roughly split into three levels: wants to buy, wants to compare, wants to understand. The mistake B2B sites make most often is treating “wants to understand” keywords as “wants to buy” keywords, then optimizing the page for the wrong audience.

When looking at search terms, also separate brand terms from category terms. Brand terms bring existing demand; only category terms bring new demand, and mixing the two in the same table blurs the picture.

If you really are going to check this layer, which two things come first

The first is to get impressions up. Until impressions reach three digits, there is no point starting a discussion about click-through rate.

The second is to pull the search terms and look at intent. You need to separate procurement-intent terms from terms that competitors, students, or people looking for reference material search. On the same site, these two groups point to completely opposite actions.

The biggest trap when judging intent is mistaking “many people search it” for “many people buy it.” In B2B these two are often inversely related, especially for terms carrying “how to choose,” “checklist,” or “comparison.”

Whether the first screen answers the search term is another thing to check on this layer. When someone clicks through from a snippet and the first screen is not about the thing in the snippet, they will bounce straight back. We wrote a more detailed version of this judgement in page structure and citation probability.

Once clicks come in but nobody fills out the form, how do you check?

We have no usable data on this layer, so we only give a checklist, not a conclusion. To be clear: discussing “form conversion rate” while clicks are 0 is meaningless — the denominator is 0.

• Can the form be submitted? Submit it yourself for real once and confirm the record arrived in the backend or the inbox.
• Are events instrumented? Without event records you cannot tell “nobody filled it in” apart from “the form is broken.”
• Does the first screen answer the search term? Someone clicking in from a snippet needs the first screen to be about the same thing the snippet said.
• Is the contact entry point prominent enough? WhatsApp, email, the form — at least one of them should be visible on the first screen.

The second of the four is the one most easily skipped. Many sites with “no inquiries” do not even record whether anyone entered the landing page, so in the end they can only judge by feel.

The form receiving submissions only settles whether leads can arrive. You also have to look at what comes in: a submission with just an email and no description of the requirement, versus one that spells out product, quantity, and destination port, have completely different follow-up costs.

If the site also has live chat or WhatsApp, remember to send a real message to test it the same way — do not just check that the icon is still lit.

There is a falsification condition here: if even your own test submission does not arrive, it is an engineering problem, not a marketing problem. Fix the engineering first; do not go and rewrite the copy.

A word on the mood in the industry. A Reddit post is titled, plainly, “How I got 17 project inquiries from a random tweet,” and in the comments /u/rufusdenne, /u/dcedrych, and /u/HawkofDarkness all press for details (public discussion, not our own case). It shows that “where do inquiries actually come from” is itself a practitioner pain point, and that a single-source story cannot be used as methodology.

Can being cited by AI count as an inquiry source?

Not directly. Internally we file this open question under ID D-016: from being cited by AI to an inquiry actually arriving, that chain still has no metric.

In this round’s breakdown of 72 answers in 2026, Tianwen was mentioned 3/72 times, in the role of “selection guide,” and the cited page was /how-to-choose-google-seo-agency-guide-2026/. In the same round, when the AI was asked directly for a list of service providers, it named 18 in total and Tianwen 0 times.

These numbers show that “being mentioned” and “being recommended” are two different things. Tianwen was mentioned 3/72 times in the role of “selection guide,” not as a service provider. Mixing them together mistakes visibility for business opportunity, and then uses visibility to explain an inquiry curve that does not exist at all.

The same round surfaced a more practical problem: AI can already publicly find versions of our facts that we have not aligned. The founding year appears as both 2017 and the website’s 2019, and the person’s name appears as both Liu Yu and Liu Pengsen. Our decided standard is to use Liu Yu consistently and not to write the registered business name; on pricing, all prices were removed from the Chinese pages and kept on the English pages.

This kind of inconsistency does not directly produce inquiries, but it makes AI unwilling to state anything definite on your behalf. There are three free ways to leave third-party verifiable traces: claiming business directory listings, technical traces (GitHub / LinkedIn), and sameAs anchoring on the site. Based on the evidence we have, their effect is to make AI willing to assert things, not to directly earn a mention, and certainly not to earn an inquiry.

Aligning facts sounds like administrative work, but it directly affects whether AI dares to cite you. When two versions of the same fact exist, the safest choice for a model is to write nothing.

Our order is to unify what the site says first, then work on off-site traces. Doing it the other way means off-site references still point at the old version, which is more expensive to change.

We also fixed the monitoring standard: record only three things — how many times Tianwen is cited, how many times szrealgood is cited, and any newly appearing cited domains. For the method, see mention and citation monitoring and the distinction between brand authority and topical authority.

Should the content format be changed to match what gets cited?

We ran one comparison: setting the two cited articles next to our three uncited ones, checked in 2026, the differences clustered in four places.

This table is only correlation, not causation. szrealgood may be cited because experiential narrative looks more like a human answer, or other factors may be at work. We do not write conclusions like “what AI likes.”

Read this table while watching for one trap: treating everything “different from mine” as “what I should change.” The cited page having fewer tables and fewer outbound links does not mean you should delete your tables and outbound links too.

Our approach is to test in small batches first, changing only one variable at a time, then going back to the panel to look for change. Change four things at once and, when something goes wrong, you will not know which one did it.

There are four directions worth testing, from our reverse-engineered recipe: a short article plus experiential narrative; first person plus an opening in the client’s own words; a question-form headline plus a number or a preview of the action; and turning data, bylines, and statistics into evidence-type content.

But none of the four has been validated yet. We have to wait for the next round of panel data before we know whether the changes had any effect. Writing in a similar style and actually being cited are separated by verification. Related discussion is in writing for AI citation and outbound links versus brand signals.

Before diagnosing, how do you make sure the observation is clean?

Diagnosing inquiries and diagnosing AI citations share one thing: the observation itself is easily contaminated, and a contaminated observation lets you reach a wrong conclusion with great confidence.

We paid tuition on the AI citation research. The first version’s six conclusions were all later voided: the six-part skeleton, the criterion being a load-bearing wall, AI preferentially citing isomorphic content, the Chinese citation pool being empty ground, AI not writing detection failure boundaries, and the entire gap table.

There were three reasons for voiding them. The baseline was contaminated: a skill catalog was injected into the runtime environment, and the dirty environment could hit 85 skills and 4 local names. The questions themselves prescribed the answer structure — writing “please give the troubleshooting approach / the basis for judgement / step by step” into the prompt fixed the shape of the answer in advance. And there was a single model and a single sample, with order effects uncontrolled.

The fix is a three-stage canary verification: the dirty environment hits 85 skills / 4 local names; then the clean environment hits 0; and finally reading a local file is denied. Only when all three stages pass are you entitled to say this round of observation is clean.

Contamination is not only a technical problem. If you hear a conclusion before you examine the site, that conclusion contaminates every judgement you make afterwards. So it is best to write the hypothesis first and then go find the data.

Another common source of contamination is the time window. When looking at clicks and impressions, confirm that all the numbers come from the same period; mixing them yields a false trend.

Labelling also needs discipline. Domain extraction must use a whitelist; otherwise “a capitalized word equals a brand” turns repetition in the body text into a new discovery. And four levels must be recorded separately: mentioned, entered the candidate list, recommended, and capability verified.

Carried over to inquiry diagnosis, the same discipline comes down to three rules. Do not draw a conclusion from one search result. Do not use one person’s statement as a sample. When reporting, give the effective N, not the surface N.

What order will we work in next?

The order does not change: get impressions up first, then look at clicks, and only then talk about form conversion. If any earlier layer has not been passed, the later ones wait.

If a priority has to be set, I would put “get impressions up” ahead of everything. Impressions are the denominator of every number that follows, and when the denominator is zero, all other discussion is empty.

• Keep running the fixed 24-question panel once every two batches of content, recording only how many times Tianwen is cited, how many times szrealgood is cited, and any newly appearing cited domains.
• The first piece of first-party evidence-type content on this site with a chance of being cited externally is the data page; how it performs will set the direction for content added afterwards.
• Claiming business directory listings, technical traces on GitHub / LinkedIn, and sameAs anchoring on the site will still be done, but at the lowest priority.
• For content format, first test short articles plus experiential narrative in a small batch, then go back to the panel data to look for change.

One more emphasis on how the panel may be used: it is an internal topic-selection tool, not a performance promise to clients, and it does not promise inquiries.

If you are also diagnosing a site that has gone a year without inquiries, you are welcome to run through this order against it. Our hands-on records are all in the research notes index, and the author’s background and this site’s positioning are in about this site and the author.

Frequently asked questions

Sources = hands-on testing (GSC 2026-10-02 diagnostic snapshot: 10/10 indexed, 0 clicks / 12 impressions over the past 28 days; three rounds of hands-on GEO reverse-engineering research, 22 questions → 72 questions → annotation, see geo/AI_ANSWER_REVERSE_ENGINEERING.md, geo/V2_ANNOTATION.tsv, geo/SZREALGOOD_DISSECTION.md, geo/probe_ai.sh; three-stage canary verification records; internal ID D-016 and the fact-alignment resolution). Public material (public discussion threads on Reddit and Xiaohongshu, including “How I got 17 project inquiries from a random tweet” and its commenters /u/rufusdenne, /u/dcedrych, /u/HawkofDarkness).

This page was machine-translated from the Simplified Chinese version and is pending human review.