When the user wants to improve E-E-A-T, add trust signals, or optimize for expertise and authority. Also use when the user mentions "E-E-A-T," "E-E-A-T signals," "experience expertise authority trust," "author bio," "YMYL," "trust signals," "expertise signals," "authority signals," "citations," "references," or "credibility." For headings, use heading-structure.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Guides E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) implementation for SEO. E-E-A-T helps search engines and users assess content quality; YMYL topics (health, finance, legal) require higher E-E-A-T.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
| Element | Meaning | Implementation |
|---|---|---|
| Experience | First-hand, real-world experience | Case studies, original research, user testimonials, "we tested" |
| Expertise | Subject-matter knowledge | Author credentials, expert quotes, technical depth |
| Authoritativeness | Recognition as a source | Backlinks, citations, author page, publisher reputation |
| Trustworthiness | Accuracy, transparency | Citations, About page, contact, HTTPS, no misleading content |
E-A-T (without Experience) is used in Featured Snippet context—Bing/Google emphasize correctness, document quality, then authority and trust. See featured-snippet.
| Element | Guideline |
|---|---|
| Real name | Full name used consistently across platforms |
| Photo | Professional headshot; compress for LCP |
| Credentials | Current role, relevant experience tied to article topic |
| Verifiable links | LinkedIn, personal site; align sameAs in Person schema |
| Author page | Dedicated page per author; bio, other articles, social |
| Lightweight action (optional) | Newsletter signup, social follow — avoid link stacking |
For co-authored, reviewed, or fact-checked content, list multiple author cards or label roles consistently (e.g. "Written by / Reviewed by").
Author entity uses Person JSON-LD with name, url, image, jobTitle, worksFor, knowsAbout, sameAs. Must match visible page content — no exaggeration or fabricated credentials. Validate with Rich Results Test. See entity-seo, schema-markup.
| Scenario | Practice |
|---|---|
| Data or statistics | Cite source inline or in References section |
| Expert quotes | Attribute; link to source or profile |
| Reference section | For 5+ citations; list at end before Related posts |
| Format | Inline links preferred; numbered refs for academic-style |
| When to include | Any claim benefiting from authority (stats, studies, definitions) |
| External links | Link to reputable sources; avoid low-quality sites |
| Signal | Use |
|---|---|
| Case studies | Real customer outcomes; Challenge→Solution→Results |
| Original research | First-party data, surveys, tests |
| First-hand testing | "We tested X"; product reviews with real use |
| User testimonials | Authentic quotes; link to full case study when available |
Topics that can significantly impact health, financial stability, or safety require higher E-E-A-T:
Guidelines: Author credentials, citations to authoritative sources, clear sourcing, regular updates, avoid speculation.
When content is AI-assisted: human review before publish; verify facts and add citations; original insights or data; avoid generic phrasing. Transparency and human refinement support E-E-A-T.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
中文简介正在准备中。当前显示原文说明。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
中文简介正在准备中。当前显示原文说明。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
中文简介正在准备中。当前显示原文说明。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
中文简介正在准备中。当前显示原文说明。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
中文简介正在准备中。当前显示原文说明。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
中文简介正在准备中。当前显示原文说明。