,
faqs,
breadcrumbItems: [{ name: “Contact”, url: “/contact” }],
});
return (
<main className=”section-shell py-10 md:py-14″>
<SchemaInjector schemas={schemas} />
<Breadcrumbs items={[{ name: “Contact”, url: “/contact” }]} />
<article className=”glass-card rounded-[2rem] p-6 md:p-8″>
<p className=”text-xs font-black uppercase tracking-[0.2em] text-[var(–brand-red)]”>Contact</p>
<h1 className=”display-title mt-3 text-5xl leading-[0.9] text-[var(–brand-blue)] sm:text-6xl”>
Contact FWC Mania
</h1>
<div className=”mt-8 grid gap-4 sm:grid-cols-2 xl:grid-cols-4″>
{quickFacts.map((fact) => (
<article key={fact.label} className=”rounded-2xl border border-[var(–line)] bg-white/85 px-5 py-5″>
<p className=”display-title text-4xl leading-none text-[var(–brand-red)]”>{fact.value}</p>
<p className=”mt-2 text-xs font-bold uppercase tracking-[0.12em] text-[var(–muted)]”>{fact.label}</p>
</article>
))}
</div>
<section className=”mt-10 rounded-[2rem] border border-[var(–line)] bg-white/85 p-6 md:p-8″>
<div className=”flex flex-col gap-3 sm:flex-row sm:items-end sm:justify-between”>
<div>
<p className=”text-xs font-black uppercase tracking-[0.2em] text-[var(–brand-red)]”>Contact Snapshot</p>
<h2 className=”display-title mt-3 text-3xl text-[var(–brand-blue)] sm:text-4xl”>
Best Reasons To Reach Out
</h2>
</div>
<p className=”max-w-xl text-sm leading-7 text-[var(–ink)] sm:text-base”>
Clear contact pages work best when they tell visitors exactly what kind of messages belong here.
</p>
</div>
<div className=”mt-8 grid gap-4 xl:grid-cols-2″>
{contactHighlights.map((item) => (
<article key={item.title} className=”rounded-[1.5rem] border border-[var(–line)] bg-[var(–bg-panel)] p-5″>
<h3 className=”display-title text-2xl text-[var(–brand-blue)]”>{item.title}</h3>
<p className=”mt-4 text-sm leading-7 text-[var(–ink)] sm:text-base”>{item.detail}</p>
</article>
))}
</div>
</section>
<div className=”mt-10 space-y-8 rounded-[2rem] border border-[var(–line)] bg-white/85 p-6 md:p-8″>
<section className=”space-y-4″>
<p className=”text-sm leading-8 text-[var(–ink)] sm:text-base”>
FWC Mania uses one main support mailbox:
Contact FWC Mania for support, factual corrections, rights questions, partnership requests, and general feedback about FIFA World Cup 2026 coverage.
Use the contact route for broken pages, missing details, mobile issues, and general site questions that stop you from using the tournament tools properly.
If you spot an error in a date, venue, ranking, team detail, or fixture note, send the exact page URL and the correction you want checked.
Commercial, editorial, and collaboration requests are welcome when the enquiry is clear about scope, timing, and what kind of cooperation is being requested.
If an image, logo, or piece of site content needs review for rights or attribution reasons, explain the issue clearly so it can be checked quickly.
);
const schemas = buildPageSchemas({
title: pageTitle,
description: pageDescription,
path:
,
imageUrl: `${SCHEMA_BASE_URL}/images/og-image.webp`,
faqs,
breadcrumbItems: [{ name:
>
<SchemaInjector schemas={schemas} />
<Breadcrumbs items={[{ name:
>
{quickFacts.map((fact) => (
<article key={fact.label} className=
>{fact.label}</p>
</article>
))}
</div>
<section className=
>
Best Reasons To Reach Out
</h2>
</div>
<p className=
>
Clear contact pages work best when they tell visitors exactly what kind of messages belong here.
</p>
</div>
<div className=
>
{contactHighlights.map((item) => (
<article key={item.title} className=
>{item.detail}</p>
</article>
))}
</div>
</section>
<div className=
>
FWC Mania uses one main support mailbox: `support@fwcmania.com`. If you’re coming from the{
}
homepage and need to flag a broken link, a missing squad player, or a factual error, email is the fastest way to get it sorted.
</p>
<p className=
Drop the exact URL, the current wording, and what the correction should be. That saves time and gets the fix live faster.
</p>
</section>
<section className=
>
A good support email answers three things instantly: what page is broken, what exactly is wrong, and is it urgent? Whether it’s a mobile layout bug, a missing venue detail, or a partnership pitch—get straight to the point.
</p>
<p className=
>
If it’s matchday and a live score is stuck, put URGENT in the subject line. If it’s a visual bug, attach a screenshot. We want to spend our time fixing the site, not guessing what the problem is.
</p>
</section>
<section className=
>
Tournament sites move fast, and the most valuable correction requests are precise ones. If you spot a team detail, venue fact, match date, or schedule issue that needs review, mention the exact line and give the source or reason for the correction. That makes it far easier to review responsibly.
</p>
<p className=
>
If your enquiry is about a broader content decision, it can help to review the{
}
section first. That page explains the site’s overall purpose and helps separate editorial suggestions from technical support messages.
</p>
</section>
<section className=
>
Partnership requests are easiest to review when they explain the goal, deliverables, timeline, and any expected placement. General “let’s collaborate” messages are much harder to evaluate than a short proposal that explains what you need and why it fits the site.
</p>
<p className=
>
If the enquiry relates to tournament coverage areas such as fixtures or reporting flow, it helps to mention the relevant product area directly. For example, some requests are better framed around the{
}
experience, while others may be closer to live match or team content.
</p>
</section>
<section className=
>
If your request involves personal data, takedowns, attribution, or a legal clarification, make that clear at the top of the email. Those topics are easier to process when the subject line and first paragraph both explain the nature of the request.
</p>
<p className=
}
first. That often answers basic questions and makes follow-up communication much clearer.
</p>
</section>
</div>
</article>
<FaqSection faqs={faqs} className=
Best Reasons To Reach Out
Clear contact pages work best when they tell visitors exactly what kind of messages belong here.
FWC Mania uses one main support mailbox: `support@fwcmania.com`. If you’re coming from the{” “}
FIFA World Cup 2026
Help us help you. If you spot a factual error, don’t just say “the page is wrong.” Drop the exact URL, the current wording, and what the correction should be. That saves time and gets the fix live faster.
A good support email answers three things instantly: what page is broken, what exactly is wrong, and is it urgent? Whether it’s a mobile layout bug, a missing venue detail, or a partnership pitch—get straight to the point.
If it’s matchday and a live score is stuck, put URGENT in the subject line. If it’s a visual bug, attach a screenshot. We want to spend our time fixing the site, not guessing what the problem is.
Corrections, Accuracy, and Editorial Requests
Tournament sites move fast, and the most valuable correction requests are precise ones. If you spot a team detail, venue fact, match date, or schedule issue that needs review, mention the exact line and give the source or reason for the correction. That makes it far easier to review responsibly.
If your enquiry is about a broader content decision, it can help to review the{” “}
Partnerships, Press, and Commercial Enquiries
Partnership requests are easiest to review when they explain the goal, deliverables, timeline, and any expected placement. General “let’s collaborate” messages are much harder to evaluate than a short proposal that explains what you need and why it fits the site.
If the enquiry relates to tournament coverage areas such as fixtures or reporting flow, it helps to mention the relevant product area directly. For example, some requests are better framed around the{” “}
If your request involves personal data, takedowns, attribution, or a legal clarification, make that clear at the top of the email. Those topics are easier to process when the subject line and first paragraph both explain the nature of the request.
Before sending that kind of note, it can be useful to read the{” “}
Privacy Policy
Terms & Conditions