datntdangson-hue/skills

Gravel Host Research Landing

Goal

Create and maintain a research-first landing page for Gravel Host. The page helps a visitor investigate Gravel Host before choosing a service. Affiliate monetization is secondary to research, evidence, clarity, and freshness.

Default target in the Levi Nguyen theme:

• URL: /brand/gravel-host/
• Template: taxonomy-brand-gravel-host.php
• CSS: assets/css/gravel-host.css
• Brand taxonomy remains the organizational entity.
• Do not reuse this template for unrelated brands.

Core positioning

Use this hierarchy:

Research → Evidence → Decision support → Deal

Never reverse it into:

Deal → promotional claims → thin review

The landing page should feel like a research dashboard, not a coupon page or generic 5,000-word blog post.

Mandatory research before writing

Research current information every time the page is materially updated.

1. Search Gravel Host's official site first.
2. Check:
   • homepage
   • game-server catalog
   • Minecraft product information
   • FiveM product information
   • ARK product information
   • legal/refund terms
   • relevant support/control-panel documentation
3. Search independent sources for:
   • customer feedback
   • complaints
   • review patterns
   • comparisons
4. Run keyword research:
   • KeywordTool.io autocomplete/suggestions/questions where available
   • Google autocomplete/SERP intent
5. Compare dates and identify contradictions.
6. Never copy a merchant claim into the research voice as a verified fact unless independently verified. Attribute provider claims when appropriate.

Current facts are snapshots, not constants

Pricing, game count, locations, hardware, policies, discounts, support claims, and ratings can change.

Always add a checked date for material facts.

Examples of facts that MUST be freshly checked before publication:

• starting price
• number of supported games
• number of locations
• Minecraft/FiveM/ARK plan pricing
• refund window and exclusions
• DDoS claim
• hardware
• support availability/response claims
• coupon value/code
• review counts/ratings

Never preserve an old number just because it exists in the template.

Source hierarchy

Prefer:

1. Gravel Host official legal/policy pages for contractual terms.
2. Gravel Host official product pages for product specs/pricing.
3. Independent primary/user-review platforms for customer experience signals.
4. Reputable independent research/reviews for context.

Do not treat affiliate review sites as authoritative evidence of quality.

If official pages conflict, explicitly flag the discrepancy with the URLs/pages and check date.

Keyword strategy

Primary entity:

• gravel host

Research clusters to validate:

• gravel host review / reviews / is gravel host good
• is gravel host legit / safe / trustworthy / reliable
• gravel host pricing / cost
• gravel host minecraft / bedrock / mods / plugins
• gravel host ark / ark survival ascended
• gravel host fivem
• gravel host performance / hardware / server locations
• gravel host control panel / dashboard / FTP
• gravel host support / discord
• gravel host refund / cancellation
• gravel host coupon / promo / discount code
• gravel host vs [competitor]

Do not create headings for every keyword variation. Merge same-intent variants naturally.

Do not create a separate URL unless SERP intent is clearly distinct and substantial enough to deserve deeper research.

Default page architecture

Use one H1 only:

Gravel Host Research

Recommended landing-page sections:

1. Hero

   • Research-first proposition
   • Last researched date
   • Explore Research CTA
   • merchant CTA secondary

2. Sticky research navigation

3. Gravel Host at a Glance

   • concise current snapshot
   • checked date
   • caveat that facts may change

4. Gravel Host Review

   • research summary
   • key findings
   • things worth checking
   • no unsupported verdict

5. Is Gravel Host Legit?

   • company/operating signals
   • policies
   • customer feedback
   • complaints/negative signals
   • safe/trustworthy queries may be nested here

6. Gravel Host Pricing

   • current plans/prices
   • billing cycles
   • what resources are included
   • checked date

7. Research by Game

   • Minecraft
   • ARK
   • FiveM
   • only retain games justified by search intent/product importance

8. Performance & Server Management

   • CPU/RAM
   • storage
   • network/DDoS
   • locations
   • control panel
   • backups/file access where supported

9. Evidence

   • What Gravel Host says
   • What I could verify
   • use this section to expose uncertainty rather than hide it

10. Refund & Cancellation

    • summarize accurately
    • include exclusions/conditions
    • link to current legal source

11. Comparison

    • only comparisons with validated intent
    • compare like-for-like configurations
    • no arbitrary winner

12. Current Deal

    • placed after substantial research
    • affiliate disclosure visible
    • verify code/discount before publishing

13. FAQ

    • derived from actual search intent
    • concise, factual answers

14. How I Researched This

    • methodology and source types

15. Research Log

    • dated material checks/updates

Writing rules

Voice:

• first-person research voice is allowed
• concise, practical, skeptical where warranted
• avoid generic AI prose
• do not use exaggerated sales language
• do not call a service "best", "perfect", "scam", "safe", "legit", or "trustworthy" as an unsupported conclusion

Prefer:

• "I found..."
• "Gravel Host states..."
• "The current policy says..."
• "I could verify..."
• "I found conflicting information..."
• "Check the current plan at checkout..."

Avoid:

• "This is undoubtedly the best..."
• "100% safe"
• "Guaranteed lag-free"
• "You should definitely buy..."
• fabricated personal testing

If no first-hand test was performed, never imply hands-on testing.

Legit/trust section standard

"Is Gravel Host legit?" must be evidence-led.

Check:

• legal entity/terms if published
• public policies
• payment/billing terms
• refund rules
• support channels
• independent customer feedback
• recurring complaint patterns
• contradictions

Do not use a review score alone as proof of legitimacy.

Review standard

A review section must explain:

• what was researched
• what evidence was used
• strengths supported by facts
• limitations/unknowns
• who a plan may suit based on requirements
• what buyers should verify

No numeric rating unless a transparent repeatable scoring methodology exists and is actually applied.

Pricing standard

For every price:

• identify the product/plan
• specify billing period when known
• date checked
• distinguish "from" price from representative configuration
• never mix VPS pricing with managed game-server pricing without labeling them separately

Refund standard

Read the current legal page in full.

Capture:

• initial refund window
• account/customer limits
• renewals
• add-ons/upgrades
• excluded products
• administrative fees
• refund method
• annual-plan treatment if applicable
• cancellation/request process

Never reduce a conditional policy to an unconditional "money-back guarantee."

Conversion standard

Affiliate CTA is allowed but must be subordinate to research.

Preferred:

• hero: secondary merchant CTA
• deal block: primary conversion area after research
• relevant contextual CTA only when it helps the user verify current pricing

Use rel="nofollow sponsored" for affiliate links.

Always include affiliate disclosure.

SEO standard

• One clear H1.
• H2/H3 reflect research intent naturally.
• No keyword stuffing.
• Add descriptive title/meta when implementation supports it.
• Internal links should connect research topics, not exist only for SEO.
• Avoid cannibalization with old/current Gravel Host URLs.
• Before creating new content, search WordPress for existing Gravel Host posts/pages.
• If an old URL is removed but still indexed, consider redirect strategy based on relevance rather than duplicating the old page.

Follow Google Search Essentials and Bing Webmaster Guidelines. Optimize for helpful, original research rather than keyword-count targets.

Landing-page UX standard

Desktop:

• max content width around 1100–1200px
• research hero
• sticky anchor navigation
• cards/tables for scanability
• evidence blocks
• generous whitespace
• deal block later in the page

Mobile:

• true single-column layout
• horizontal-scroll research nav
• 2-column compact stats where readable
• 1-column research cards
• full-width primary actions
• readable body typography
• no desktop table overflow

Keep typography and spacing consistent with the Levi Nguyen homepage while allowing the research page to be wider.

WordPress implementation

For levinguyen.com:

• use taxonomy-brand-gravel-host.php for Gravel Host only
• keep generic taxonomy-brand.php for other brands
• keep Gravel Host styles in assets/css/gravel-host.css
• enqueue that stylesheet only on is_tax('brand', 'gravel-host')
• version CSS with filemtime()
• do not put Gravel Host-specific CSS into the global stylesheet unless there is a shared design-system reason
• preserve homepage behavior

Before editing:

1. Read the current template, CSS, functions.php and brand helpers.
2. Check git status.
3. Make focused edits.
4. Run PHP lint.
5. Run git diff --check.
6. Inspect responsive behavior when possible.
7. Do not push unless the user asks.

Quality gate

Before calling the page ready, verify:

• WordPress has no competing live Gravel Host page/post with the same intent.
• Keyword clusters were freshly checked.
• Current official product facts were freshly checked.
• Legal/refund policy was freshly read.
• Pricing has dates/context.
• Provider claims are attributed where needed.
• Independent feedback includes both positive and negative signals.
• No fabricated hands-on experience.
• Research appears before the deal.
• Affiliate disclosure is visible.
• Affiliate links use sponsored/nofollow.
• H1/H2/H3 are coherent and non-spammy.
• Desktop/mobile CSS is complete.
• Template is Gravel Host-specific.
• PHP lint passes.
• git diff --check passes.
• Research Log is updated.

Output when invoked

Report:

1. research status
2. keyword/intent map
3. material facts and conflicts found
4. proposed/updated landing-page sections
5. files changed
6. validation status
7. whether changes are pushed or still local