SEO Evaluator v2.1（电商页面评估）

Ecommerce AI directory: homepage SEO evaluation

1. Page and retrieval metadata

Scope: the public English homepage and Chinese equivalent, for ecommerce operators comparing AI tools, agents and Skills. The supplied primary query is “ecommerce AI tools.” Business inputs are synthetic; the named public website was inspected live. No site changes were made.

Field	English	Chinese
Requested and final URL	https://ecomagenttools.com/	https://ecomagenttools.com/zh
HTTP response	200; text/html; charset=utf-8	200; text/html; charset=utf-8
HTML language	en	zh-CN
Canonical	Self-referencing root URL	Self-referencing /zh URL
Robots meta	index, follow	index, follow
X-Robots-Tag	Not present in captured response	Not present in captured response
Raw HTML bytes	111,110	111,657
Links / images	120 / 28 in both raw and rendered HTML	120 / 28 in both raw and rendered HTML
H1 count	1	1
JSON-LD types	WebSite, Organization, nested SearchAction	WebSite, Organization, nested SearchAction
Language alternates	en, zh, x-default	Same reciprocal set

Sources: English homepage, Chinese homepage. Captured fields and collection time are in page-evidence.json; raw/rendered comparisons are in technical-summary.json. The original homepage requests ended at their requested URLs. Individual redirect hops were not logged. A separate /zh/ request ended at /zh; see link-checks.json.

The browser inspection used the initial rendered page without interaction. Raw HTML was separately retrieved and parsed. Matching counts do not prove identical DOMs; the main heading, metadata and discovery anchors were also checked in source. No field performance measurement was collected.

Title and description inventory

English title: AI Tools for Ecommerce by Workflow | EcomAgentTools

English description: Find ecommerce AI tools for support, content, marketing and operations. Start with your workflow, then explore the resources that fit your next task.

Chinese title: 电商 AI 工具推荐与独立评测｜EcomAgentTools

Chinese description: 对比电商 AI Agent、AI 技能与即用提示词，覆盖客服、营销、商品内容、库存、定价和履约。查看独立评分、价格、平台集成与应用场景，帮助 Shopify、Amazon、WooCommerce 店铺更高效完成工具选型。

Both are present and distinct within the two-page homepage sample. The English text accurately describes workflow-led discovery. The Chinese description positions the wider directory as a comparison resource; it should not be read as confirmation that every listed tool supports every named platform. The visible FAQ explicitly says compatibility varies by resource. Keep both titles and descriptions; no evidenced defect warrants replacements. These are search-result inputs, not guaranteed display text: Google generates title links automatically and may select different snippet text. Sources: English, Chinese, Google title-link guidance, Google snippet guidance.

2. Executive finding

Keep the existing technical foundations and prioritize selection clarity. No verified SEO issue is supported by the inspected sample. Both homepages provide crawlable discovery links, appropriate language canonicals, reciprocal alternates, and content aligned with the requested topic. These observations establish public crawl/indexing signals, not actual Google index inclusion. Sources: English, Chinese, robots.txt, sitemap.

The page fits a discovery/comparison interpretation of “ecommerce AI tools”: eight workflow routes, separate resource lists, tool summaries, setup difficulty, FAQs and guides help operators start a shortlist. This is an editorial assessment of task fit, not a measured search-demand or ranking conclusion. The main improvement is to help readers interpret resource types and scores before choosing a route.

Evidence label	Actionable findings	Priority
VERIFIED	0 issues	None
LIKELY	0 issues	None supported
EDITORIAL	3 opportunities	2 now; 1 next
UNAVAILABLE	4 check groups	Obtain evidence before drawing conclusions
APPENDIX	3 check groups	Separate from SEO issue count

Priorities reflect clarity and ease of implementation, not forecast traffic or revenue. No universal SEO score is assigned.

3. VERIFIED issues

None supported. Do not open a technical remediation ticket solely because there are 120 anchors, 28 images, a large HTML response, or several resource sections. These counts do not establish crawl, ranking or performance failures. Evidence: technical summary.

4. LIKELY issues requiring confirmation

None supported. No ranking, engagement or index data were supplied, so the report does not infer underperformance from the page design. Missing data are recorded below rather than presented as likely defects.

5. EDITORIAL opportunities

E1 — Now: clarify the Chinese workflow heading

Evidence and reproduction: On the Chinese homepage, the workflow H2 says “按工作流浏览 AI Agent,” while its explanatory paragraph and destinations cover agents, Skills, prompts and SaaS tools. The English equivalent uses the broader “Browse AI Tools by Ecommerce Workflow.” This is a scope-label mismatch for readers, not a technical indexing error.

Recommendation and finished Chinese copy: Replace that H2 with:

按电商工作流查找 AI 工具

Retain the existing eight workflow links and explanatory paragraph.

Owner: Chinese content editor. Acceptance: the new heading appears in source and rendered HTML above the eight category cards; all category destinations remain intact; the label no longer implies the section contains only agents.

E2 — Now: explain resource types beside the selection lists

Evidence and reproduction: The English and Chinese homepages group Prompts, Skills and SaaS separately. The English introduction already mentions setup and review, and both FAQs explain that Skills can need a compatible agent. A compact explanation beside the lists would reduce the need to infer the difference from scattered text. This is reader guidance, not missing mandatory SEO content.

Recommendation: Insert the following short guide before the three resource lists, with each resource name linking to its existing directory. Keep the live title and meta description unchanged.

Resource	English customer-facing copy	Chinese customer-facing copy	Existing destinations
Prompts	Start with a prompt when you need instructions for a task. Check the input it needs and review the output.	提示词：适合先完成一个具体任务。使用前核对所需资料，生成后检查结果。	/prompts; /zh/prompts
Skills	Choose a Skill for a reusable procedure. Check the compatible agent, installation steps and required access.	技能：适合重复执行一套操作步骤。使用前核对兼容的智能体、安装方法和所需权限。	/skills; /zh/skills
SaaS tools	Explore SaaS tools for hosted software. Check platform support, pricing and setup before subscribing.	SaaS 工具：适合寻找托管软件。订阅前核对支持的平台、计费方式和配置要求。	/saas-tools; /zh/saas-tools

Owner: Content editor and frontend developer. Acceptance: each of the six localized directory destinations is an ordinary <a href> link; the guide appears before the lists on desktop and mobile; it makes no blanket compatibility or automation claim. Ask a small group of operators to explain which resource they would choose for a one-off draft versus a repeatable procedure; record their answers without assuming a conversion benefit.

E3 — Next: surface score interpretation at the decision point

Evidence and reproduction: Homepage lists show scores such as 81/100 and 85/100 alongside popularity positions. The text above the lists explains that Skill and SaaS popularity order uses recent Google Search clicks, while prompts use catalog recommendation order. The editorial policy separately describes different scoring dimensions for tools and Skills and explains that community weights vary. A footer policy link exists; this recommendation brings it nearer the numbers. The stated click-based ordering is observable copy, but its underlying data were not audited.

Finished copy beside the lists:

English:

Popularity order and scores measure different things. See how tool and Skill scores are calculated before comparing resources.

Chinese:

热门排序与评分衡量的内容不同。比较资源前，请先了解工具与技能的评分方法。

Link “how tool and Skill scores are calculated” to /about/editorial-policy, and “评分方法” to the existing localized policy destination /zh/about/editorial-policy after confirming it resolves correctly. Do not invent a reporting window for “recent”; the data owner should supply the actual window before making the existing ordering explanation more specific.

Owner: Editorial lead, frontend developer and ranking-data owner. Acceptance: methodology is reachable beside the scores with a crawlable link; localized destination returns the intended policy; wording distinguishes popularity from editorial/community assessment; any added reporting window agrees with the actual ordering configuration. No claim of independently verified search-click totals is added.

6. UNAVAILABLE checks

ID	Check group	Evidence needed and decision affected
U1	Google index inclusion and selected canonical	Authorized Search Console URL Inspection for both homepages. Public 200 responses, robots permission and declared canonicals do not establish inclusion or Google's chosen canonical.
U2	Query performance, snippet display and business outcomes	Search Console query/page data plus authorized analytics and defined directory-comparison events. Needed to judge search-intent performance, CTR, language-specific demand or conversion effect.
U3	Field performance	CrUX or authorized real-user measurements. No field CWV, INP or performance pass/fail conclusion is available; HTML byte size alone cannot provide one.
U4	Comprehensive coverage and operational claims	A representative site crawl plus sitemap comparison for orphan status and sitewide duplicates; ordering configuration/source data to verify click-based popularity; primary product evidence to substantiate individual tool claims. This homepage sample cannot validate the full catalog, filters, pagination, all parameter routes or feed consistency.

No authenticated data were accessed. These gaps limit conclusions; they are not defects to fix speculatively.

7. APPENDIX checks

A1 — Media layout and accessibility. Both raw homepages have alt attributes on all 28 images; 15 images per page lack at least one HTML width/height attribute. Some images use lazy loading. This does not establish layout shift: CSS may reserve space. Have the frontend owner inspect reserved aspect ratios during loading before changing markup. Acceptance: essential images have appropriate alternative text and stable reserved space; measure layout shifts if a performance concern emerges. Source: technical summary, homepage. No image-byte or visual-accessibility audit was completed.

A2 — Social preview. The English page declares Open Graph title, description, URL and image, plus a summary_large_image Twitter card; Chinese metadata are captured in the evidence. Presence is verified, but image dimensions, network availability and platform rendering were not validated. Preview both languages in the relevant sharing interface before changing assets. Source: page evidence, English, Chinese.

A3 — Outbound links and interaction accessibility. Link href, rel and target attributes were captured, but external destinations, sponsorship relationships, keyboard menus and screen-reader behavior were not comprehensively audited. No security or accessibility failure is asserted from empty visible anchor text alone; accessible names can come from other attributes. Acceptance for a separate review: verify accessible names and keyboard operation, and apply relationship attributes according to actual link relationships. Source: page evidence.

8. Passed checks

• VERIFIED — Crawl/index signals: both homepages return 200 with index, follow; captured responses have no X-Robots-Tag. robots.txt allows the homepages and declares the fetched sitemap. Both homepage URLs appear there.
• VERIFIED — Canonical consistency: raw and rendered homepages declare their own language URLs. The sitemap agrees. The tested tracking-query URL retains the root canonical; /zh/ resolves to /zh. This is a bounded variant sample. Link checks, Google canonical guidance.
• VERIFIED — International signals: both pages carry reciprocal en/zh/x-default annotations, consistent with sitemap alternates; each language keeps its own canonical. English, Chinese, sitemap.
• VERIFIED — Heading structure: both use one H1, followed by workflow and resource H2 sections, H3 resource groups/cards, further H2 FAQ and guide sections, and H3 questions/articles. No skipped heading level appears in the captured sequence. H1s are “Find AI Tools for Ecommerce by Workflow” and “帮你找到真正适合的AI电商工具.” This is understandable structure, not proof of accessibility conformance. Heading inventory.
• VERIFIED — Internal discovery: category, prompt, Skill, SaaS and guide routes use anchors with hrefs in initial HTML. Sampled product-content category pages in both languages, the English Product Description Generator Skill, DeepL tool and editorial policy all return 200. These sample results do not certify every link. Link checks, technical summary.
• VERIFIED — Rendering boundary: both H1 texts, canonical and language annotations are in raw HTML as well as the rendered DOM; source has 120 anchors on each page. Primary discovery does not depend solely on clicking a JavaScript control. Tab interaction and all hidden content were not tested. Technical summary.
• VERIFIED — Structured-data syntax: captured homepage JSON-LD parses successfully and contains WebSite and Organization with nested SearchAction. This is not rich-result eligibility validation. Product/Offer schema is not required simply because this is a tool directory homepage. Schema evidence.

9. Checkbox action plan

Now

• E1 — EDITORIAL: Chinese editor changes the workflow H2 to the supplied broader label; confirm source/rendered text and all eight links.
• E2 — EDITORIAL: Editor and developer add the supplied resource-type guide in both languages; confirm crawlable directory links and mobile readability.

Next

• E3 — EDITORIAL: Editorial lead surfaces the scoring explanation beside scores; verify the Chinese policy destination and any data-window wording before release.
• A1 — APPENDIX: Frontend owner checks reserved image space; change dimensions only where the loading inspection supports it.

Monitor

• U1/U2 — UNAVAILABLE: When authorized data become available, inspect index/canonical decisions and query-level results for each language. Evaluate outcomes against a recorded baseline; no lift is assumed.
• VERIFIED regression checks: After changes, recheck 200 responses, canonicals, robots, alternates, sitemap consistency and important anchor destinations against the captured baseline.
• U3 — UNAVAILABLE: Use field data for a performance decision before treating response size or missing dimensions as a CWV failure.

Completed supporting files: page-evidence.json contains public response and DOM evidence; technical-summary.json contains computed raw/rendered checks; link-checks.json contains the bounded destination and variant sample. The copy above is a finished draft for review, not a published change.