Keine Karriere-Subdomain Gefunden — Causes, Impacts & How to Fix

Introduction

“Keine Karriere-Subdomain Gefunden” is German for “No Career Subdomain Found.” It means a browser, SEO tool, or HR platform cannot locate a company’s career page at its expected subdomain address (e.g., karriere.company.com). The cause is almost always a DNS misconfiguration, an expired SSL certificate, a botched website migration, or an ATS platform disconnect. It is fixable — usually within hours — but the longer it sits unresolved, the more it quietly damages your search rankings and recruitment pipeline.

What This Error Actually Means

You’re staring at the phrase “keine karriere-subdomain gefunden” and wondering what went wrong. First, the translation: it’s German, and it simply means “no career subdomain found.”

Keine = No. Karriere = Career. Subdomain = Subdomain. Gefunden = Found.

That’s it. No virus, no hack, no catastrophic system failure. What you’re seeing is a technical notification — from an SEO audit tool, an HR analytics dashboard, or a recruiting platform — telling you that it went looking for a company’s career page at a specific subdomain address (karriere.company.com, jobs.company.com, or similar) and came back empty-handed.

The message surfaces in a few different ways. A job seeker might click a careers link they found on LinkedIn or in a Google result and land on a dead page. A web administrator running a routine health check might spot it in a monitoring report. An SEO professional might discover it during an audit and immediately start calculating how much organic traffic has already been lost. An HR manager might get an alert from IT and want to know how badly the recruitment pipeline has been affected.

It looks alarming — especially if you weren’t expecting German — but the situation is almost always recoverable. The trick is understanding exactly what broke and where to look.

Who Encounters It — and What They Actually Need

Here’s something worth acknowledging upfront: different people stumble onto this error for completely different reasons, and they need completely different answers.

If you’re a job seeker, you don’t care about DNS records or SSL certificates. You just want to find the company’s open positions and figure out how to apply. Jump to Section 7 — it has five practical ways to reach the career page even when the subdomain is broken.

If you’re a web administrator or IT professional, you need a clear diagnostic process and a step-by-step fix. Section 8 is written specifically for you, covering DNS, SSL, server configuration, and redirects in a logical order.

If you’re an HR manager or recruiter, you’ve probably just been told by IT that the career site is down and you need to understand the business impact quickly. Sections 5 and 6 explain what this means for your search rankings and your hiring pipeline — and how long recovery typically takes.

If you’re an SEO professional, you’re likely already calculating the crawl and indexing damage. Sections 5, 10, and 11 cover the technical SEO angle in depth, including subdomain vs. subfolder architecture and the Google for Jobs implications.

This guide covers all of it in one place.

Understanding Career Subdomains

Before going any further, it helps to be clear on what a career subdomain actually is and why companies use them.

A subdomain is simply a prefix attached to a root domain that creates a distinct section of a website with its own address. If a company’s main website is company.com, their career subdomain might be karriere.company.com, careers.company.com, or jobs.company.com. The key thing to understand is that a subdomain can — and very often does — live on a completely different server than the main website.

That’s exactly why large and mid-sized companies tend to use them for career pages. When you’re running an enterprise HR platform like SAP SuccessFactors, Workday, Oracle Recruiting Cloud, Greenhouse, or Lever, your career portal is actually hosted on that platform’s infrastructure. The company maps its own branded subdomain to the platform using a DNS record, so candidates see careers.company.com in their browser while the content is served from the ATS provider’s servers behind the scenes.

This setup works well — when it’s maintained. The career subdomain hosts everything candidates need: job listings, application forms, employer branding content like culture videos and team photos, the company’s stated values and interview process, and often a talent community sign-up. When the subdomain breaks, all of that disappears simultaneously for everyone — job seekers, search engine crawlers, and the HR team trying to track applications.

The alternative is a career subfolder, where all that content lives at company.com/karriere or company.com/careers. Whether you should use a subdomain or a subfolder is actually one of the most consequential decisions in career site SEO — and we’ll settle that debate properly in Section 10.

Why This Error Happens: The 7 Real Causes

The “keine karriere-subdomain gefunden” error almost always traces back to one of seven failure points. Knowing which one you’re dealing with determines where to start the fix.

A Bad DNS Record

This is far and away the most common cause. The Domain Name System is what translates karriere.company.com into an actual server IP address. If the DNS record — either an A record pointing to an IP or a CNAME record pointing to another domain — is missing, incorrect, or stale from a recent change, the browser gets no valid answer, and the page never loads.

What’s sobering is how little it takes to cause this. A single mistyped character. An IP address that changed when the company switched hosting providers. A CNAME that still points to an old ATS hostname that no longer exists. DNS is unforgiving with precision.

An Expired or Missing SSL Certificate

Modern browsers don’t just warn users about missing SSL certificates — they actively block access. If the SSL certificate covering the career subdomain has expired, or was never configured to include that subdomain in the first place, visitors will hit a security wall before they ever see a job listing. Depending on browser settings, they’ll either see a security warning page or, in some configurations, the “keine karriere-subdomain gefunden” message directly.

This is especially common when companies use individual certificates for each subdomain rather than a wildcard certificate that covers everything under *.company.com automatically.

A Website Migration That Left Broken Links Behind

This is the most heartbreaking cause because it’s entirely preventable. A company relaunches their website, rebrands, switches to a new CMS, or migrates from one ATS to another — and in the chaos of the project, nobody sets up 301 redirects from the old subdomain URLs to the new locations.

Those old URLs live on, though. They’re embedded in LinkedIn job posts. They’re saved in Google’s index. They’re in email campaigns sent six months ago. They’re in bookmarks on candidates’ laptops. Every person following those links hits a dead end, and every time Google’s crawler visits them, it gets a 404 and inches closer to removing those pages from its index entirely.

The Subdomain Was Simply Never Created

Sometimes the message isn’t an error at all — it’s just a factual observation. Smaller companies, startups, and personal brands often don’t have a career subdomain because they’ve never set one up. They post jobs on LinkedIn, Indeed, or their Facebook page and don’t maintain a dedicated recruiting portal. When an SEO tool scans the domain and reports “keine karriere-subdomain gefunden,” it’s not telling you something broke. It’s telling you something was never built. No action needed — unless you decide to create one.

The ATS Platform Connection Broke

Enterprise ATS platforms like SAP SuccessFactors, Workday, and Greenhouse host the actual career portal on their servers. The company’s branded subdomain connects to that server using a CNAME DNS record. This connection is surprisingly fragile. If the CNAME wasn’t maintained after the company switched ATS providers, or if the platform changed its hosting configuration and the CNAME target hostname changed, the branded subdomain goes nowhere. The platform is still there and working — it’s just no longer connected to the subdomain the company’s audience knows.

The Web Server Isn’t Configured to Handle the Subdomain

Even with a perfect DNS record, if the web server hasn’t been explicitly configured to accept requests for the career subdomain, those requests go unanswered. Apache and Nginx — the two most common web servers — use configuration files called virtual host blocks to map incoming requests to specific content. If there’s no entry forkarriere.company.com, the server doesn’t know what to do with traffic arriving at that address, and the connection fails. This often happens after a server update, a migration to a new hosting infrastructure, or when someone’s sites-available configuration got accidentally overwritten.

Domain Expiry or Registrar Migration

Finally, companies that let their domain registration lapse, or that switch domain registrars without carefully migrating all DNS settings, can lose subdomain configurations entirely. The main domain often gets restored quickly when someone notices it’s down, but subdomain-specific records like the career portal CNAME frequently don’t make it through the migration intact.

What It Does to Your SEO (And It’s Not Pretty) {#seo-impact}

For most companies, the career page is one of the most SEO-valuable sections of their entire website. Job seekers actively search for terms like “[Company Name] jobs,” “[Company Name] open positions,” and role-specific queries like “[Company Name] software engineer hiring” — and these searches carry extremely high intent. When the career subdomain breaks, all of that organic real estate starts eroding almost immediately.

Google Stops Indexing the Pages

Googlebot crawls URLs continuously from its index. When it repeatedly visits a dead subdomain and gets 404 errors or connection timeouts, it interprets those as signals that the content no longer exists. After enough failed attempts — which happen faster than most people expect — Google begins deindexing the affected pages. Once a job listing or career page drops out of the index, it disappears from search results entirely, including from Google for Jobs, which is where many high-intent candidates find open roles directly in search results.

Career pages that have been carefully optimized with JobPosting structured data (JSON-LD schema) are particularly vulnerable here, because the schema can only be validated by Google when the page is actually accessible. A broken subdomain means all of that structured data markup goes to waste, and the company’s listings vanish from Google for Jobs without warning.

Domain Authority Gets Stranded

When career content lives on a subdomain, it builds its own SEO equity somewhat independently from the root domain. That means backlinks pointing to karriere.company.com job pages — from job boards, university recruiting pages, press coverage, LinkedIn — contribute to the subdomain’s authority rather than flowing through to strengthen company.com. When the subdomain breaks and eventually gets deindexed, that accumulated authority is lost. There’s no automatic transfer back to the main domain.

Google Search Console Fills With Errors

If the career subdomain was verified in Google Search Console — which it should be — the GSC dashboard will start populating with crawl errors, coverage issues, and server error flags within days of the subdomain going down. Beyond being ugly to look at, these errors confirm that Google has noticed the problem. The impression data stops flowing in, which makes it impossible to monitor recovery progress and understand how much organic visibility has been lost.

The Core Web Vitals Signal Disappears

Google’s Page Experience ranking signals depend on real-user CWV data. A subdomain that’s returning errors generates no usable performance data, which gradually removes it from Core Web Vitals assessments. This is a secondary concern compared to indexing, but it compounds the overall signal degradation over time.

The bottom line is simple: every day the career subdomain stays broken is another day of ranking positions eroding, organic traffic declining, and the recovery timeline lengthening.

The Employer Branding Damage Nobody Talks About

The SEO impact is measurable and serious. But there’s another dimension of damage that’s harder to quantify and, if anything, even more consequential: what this error does to how candidates perceive your company as an employer.

Think about how candidates actually behave when evaluating a job opportunity. They research the company. They read Glassdoor reviews. They check LinkedIn. And they visit the career page — often as one of their very first stops — to understand what the company actually says about itself as a workplace. What the culture looks like. What benefits are offered? What the team seems like. This is the page where employer brand promises live.

When a motivated candidate arrives at that page and finds it broken, the psychological effect is immediate. The company looks disorganized. In the worst interpretations, it looks financially troubled. In a competitive talent market where skilled candidates are evaluating multiple opportunities simultaneously, most will not troubleshoot the error, try a different URL, or email HR asking for an alternative link. They will simply open the next tab.

The numbers behind this are significant. Companies in competitive hiring markets can experience a 30 to 40 percent drop in application volume before anyone on the HR team even realizes the career page is down. Not because candidates became less interested, but because the front door to the application process was quietly broken the whole time.

And unlike an SEO ranking drop, which at least shows up in dashboards and data, the employer branding damage is invisible until you’re looking at a thin hiring pipeline weeks later, trying to figure out what changed.

If You’re a Job Seeker: 5 Ways Around the Broken Page

If you’ve clicked a careers link and hit this error, the good news is that the job listings you’re looking for almost certainly still exist somewhere — the company’s career portal is just temporarily unreachable at that specific address. Here are five reliable ways to get around the problem.

• Go directly to the company’s homepage. Navigate to company.com and look for a “Careers,” “Jobs,” “Work With Us,” “Stellenangebote,” or “Opportunities” link in the main navigation or in the footer. Most companies link to their career section prominently from the homepage, and if the career section has moved to a new URL, the homepage link will reflect that.
• Search Google. Open a new tab and search for “[Company Name] careers” or “[Company Name] jobs.” Google’s index sometimes caches working versions of career pages even when the subdomain is temporarily down, and search results will surface the current working URL directly.
• Check LinkedIn. Every company on LinkedIn has a “Jobs” tab on its company profile page. LinkedIn hosts those listings on its own infrastructure, completely independently from the company’s website. Even if the company’s entire career site is down, its LinkedIn job postings will still be fully accessible, and applicants can apply directly through LinkedIn.
• Try job aggregators. Platforms like Indeed, Glassdoor, StepStone, XING, and Monster pull listings from thousands of companies. The company’s open positions are likely listed there with their own application links that don’t depend on the company’s subdomain working correctly.
• Reach out directly. If you’re genuinely interested in a specific company, a short, professional message to someone on their Talent Acquisition or HR team on LinkedIn — explaining that you found the careers link broken but that you’re interested in opportunities — often lands well. It’s memorable, it demonstrates initiative, and it sidesteps the technical problem entirely.

If You’re a Web Admin: The Complete Fix Guide

The fix for “keine karriere-subdomain gefunden” follows a logical diagnostic sequence. Don’t start making changes before you know what’s actually broken — each cause has a different solution, and fixing the wrong thing wastes time.

Step 1: Identify the Exact Error Type

Open your browser’s developer tools (F12 or right-click → Inspect), go to the Network tab, and try to load the career subdomain URL. The HTTP response will tell you where to focus:

• ERR_NAME_NOT_RESOLVED means DNS is failing. The subdomain isn’t resolving to any IP address.
• ERR_SSL_PROTOCOL_ERROR or an SSL certificate warning means the certificate is the problem.
• 404 Not Found means DNS and SSL are working, but the server has no content configured for this subdomain.
• Connection Timed Out usually means the server itself isn’t responding.
• A 301 or 302 redirect loop means redirect rules are conflicting with each other.

Step 2: Fix the DNS Record

Log into your DNS management panel — whether that’s Cloudflare, Route 53, GoDaddy, Namecheap, or wherever your domain is managed — and check whether a record exists for the career subdomain. Look for either an A record (pointing directly to an IP address) or a CNAME record (pointing to another hostname, which is how most ATS-hosted career sites work).

If the record is missing entirely, create it. If it exists but the IP address is wrong because you changed hosting providers, or the CNAME target is outdated because your ATS changed its hostname, update it to the correct value. After any DNS change, allow up to 72 hours for propagation to spread globally, though changes often take effect within minutes.

To verify propagation from outside your own network, use MXToolbox (mxtoolbox.com) or WhatsMyDNS (whatsmydns.net) — both show how the subdomain resolves from multiple geographic locations simultaneously.

Step 3: Resolve Any SSL Issues

Use SSL Labs (ssllabs.com/ssltest/) or SSL Shopper (sslshopper.com/ssl-checker.html) to test whether a valid SSL certificate covers the career subdomain. Pay specific attention to the Subject Alternative Names (SAN) list in the certificate details — every subdomain that needs HTTPS coverage must be explicitly listed there.

If the certificate has expired, renew it through your hosting provider or Certificate Authority. If the subdomain was never added to the certificate, reissue it with the subdomain included. Going forward, a wildcard certificate for *.company.com is strongly recommended — it automatically covers any subdomain without individual certificate management overhead.

Step 4: Check the Web Server Configuration

If DNS resolves correctly and SSL is valid, but the page still won’t load, the problem is likely in the web server configuration. For Apache, check /etc/apache2/sites-available/ for a virtual host file that defines ServerName karriere.company.com and make sure it’s enabled. For Nginx, check /etc/nginx/sites-available/ for a server block with server_name karriere.company.com. If neither exists, the server has no instructions for what to do with requests arriving at that address.

After making configuration changes, restart the web server:

# Apache
sudo systemctl restart apache2

# Nginx
sudo systemctl restart nginx

Step 5: Set Up Redirects If the URL Has Changed

If the career page moved — say, from karriere.company.com to company.com/karriere — and 301 redirects were never configured, now is the time to fix that. Proper 301 redirects are critical: they tell both users and search engines where the content has moved, preserve any accumulated SEO equity, and ensure nobody ever hits a dead end following an old link.

In Apache’s .htaccess or virtual host configuration:

RewriteEngine On
RewriteRule ^(.*)$ https://company.com/careers/$1 [R=301,L]

In Nginx:

server {
    server_name karriere.company.com;
    return 301 https://company.com/careers$request_uri;
}

Test the redirects after implementing them using Redirect Checker (redirect-checker.org) or the Network tab in browser developer tools to confirm the redirect chain is clean and ends at the right destination.

Step 6: Verify Your ATS Platform Integration

If you use an enterprise ATS that hosts the career content on its own servers, log into the admin panel and confirm that the custom domain configuration is still active and correctly set up. ATS platforms occasionally change their hosting infrastructure, which means the CNAME target hostname they require you to point to can change without obvious notification. Check with your platform’s support team if you’re unsure whether the current CNAME target is still correct.

Step 7: Request Re-Indexing in Google Search Console

Once the subdomain is fully restored and accessible, don’t just wait for Google to rediscover it on its own schedule. Log into Google Search Console, use the URL Inspection tool on the career subdomain’s main URL, and click “Request Indexing.” Do the same for your key job listing pages. This accelerates the re-crawl process significantly and shortens the SEO recovery window.

SAP SuccessFactors Career Site Builder

SAP SuccessFactors deserves its own section because it’s one of the most widely used enterprise HR platforms globally, and its Career Site Builder (CSB) module has a specific architecture that produces its own variant of this error.

Here’s how CSB hosting works: the actual career content is served from SAP’s infrastructure, while the company maps its own branded subdomain to that content using a CNAME record in its DNS panel. This means the DNS record lives on the company’s side, and the content is served from SAP’s side — and if either part of that equation breaks, the career site goes dark.

The most common CSB-specific causes include an outdated CNAME pointing to a deprecated SAP jobs2web hostname, a mismatch between the domain configured inside CSB’s Admin Center and the actual subdomain in DNS, an SSL certificate that wasn’t regenerated after a domain configuration change, and a CDN cache serving stale content after a recent site republish.

To fix it, start in SAP SuccessFactors Admin Center and navigate to Career Site Builder → Admin → Site Configuration → Domain Settings. Confirm that the domain configured there exactly matches your actual DNS CNAME setup, including case sensitivity. Then check the CNAME record in your DNS panel and confirm it points to SAP’s current required hostname for your environment.

If the SSL certificate needs to be refreshed on the CSB side, use the Regenerate Certificate option within the site settings. After any DNS changes, allow 24 to 72 hours for full propagation. After any content changes, republish the CSB site and flush the CDN cache to ensure the latest version is being served.

One important SAP-specific note: SAP SuccessFactors does not support using a root domain (e.g., company.com) as the career site address — only a proper subdomain (e.g., careers.company.com) is supported. If your configuration is attempting to use a root domain, that is the source of the error and it must be reconfigured.

Subdomain or Subfolder? The SEO Answer Is Clear {#subdomain-vs-subfolder}

One of the most important decisions underlying all of this is whether companies should be using career subdomains at all. This debate has been going on in the SEO community for years, but the practical evidence in 2026 points clearly in one direction.

When career content lives in a subfolder — at company.com/karriere/ or company.com/careers/ — it benefits directly from the main domain’s full authority. Every backlink pointing to company.com from anywhere on the internet also strengthens the career pages. Internal links from the main site pass equity directly to job listings. The crawl budget isn’t split across two separate domains. The technical configuration is simpler — no separate DNS records, no subdomain-specific SSL certificates, no separate virtual host configuration to maintain. And most importantly, the entire class of “keine karriere-subdomain gefunden” errors becomes impossible, because there’s no subdomain to break.

Career pages on a subdomain, by contrast, are treated by Google as a largely independent website. The main domain’s authority doesn’t flow through as freely. Backlinks have to be built separately for the subdomain to accumulate its own ranking power. And as we’ve seen throughout this guide, the technical infrastructure around a subdomain requires ongoing maintenance that often falls through the cracks between IT and HR teams.

That said, many companies have no practical choice. If you’re running SAP SuccessFactors, Workday, Oracle Recruiting Cloud, or another enterprise ATS that hosts content on its own servers, a subdomain is technically necessary. The platform can’t be embedded into your main website’s folder structure because it doesn’t live on your server.

If you’re in that situation, the subfolder isn’t an option — but the maintenance standard has to be higher. Automated DNS monitoring, wildcard SSL certificates, documented change protocols, and quarterly technical audits aren’t nice-to-haves for career subdomains. They’re the cost of keeping an externally hosted career portal reliably reachable.

If you’re a smaller company or startup that hasn’t yet committed to an enterprise ATS and you’re designing your career section from scratch, the answer is straightforward: build it as a subfolder. You’ll rank better, maintain it more easily, and never have to worry about this specific class of error.

How to Make Sure This Never Happens Again

Fixing the error is the easy part. Making sure it doesn’t happen again requires treating the career portal with the same operational seriousness as any other revenue-critical system.

• On the monitoring side, set up automated uptime checks for the career subdomain using a tool like UptimeRobot or Pingdom. Configure it to alert someone immediately — not daily, not in a weekly report, but immediately — when the subdomain stops responding. The sooner you know, the less SEO and hiring pipeline damage accumulates. Five minutes of response time is vastly better than discovering the problem when HR notices application volume has dropped over the past three weeks.
• On the SSL side, switch to automated certificate renewal if you haven’t already. Let’s Encrypt with Certbot handles this reliably for free. If your hosting provider manages certificates, enable their auto-renewal option. A wildcard certificate for *.company.com eliminates the need to manage subdomain-specific certificates individually and is worth the investment.
• On the change management side, establish a formal protocol that requires IT sign-off on any infrastructure change touching the career subdomain — migrations, redesigns, ATS platform switches, and hosting moves. The rule should be simple: 301 redirects go live before old URLs are decommissioned, not after. After any infrastructure change, someone tests the career URL from multiple browsers, devices, and locations before the project is considered done.
• On the audit side, run a proper technical SEO crawl of the career site quarterly using Screaming Frog, Ahrefs, or Semrush. Manually verify that every career link on the main website, LinkedIn company page, Indeed company profile, and email signatures resolves correctly each month. Check Google Search Console weekly for coverage issues and structured data errors on career pages.
• On the organizational side, the single most effective prevention measure is also the simplest: designate one named person who owns the career site’s technical health. Not a team, not a shared responsibility — one person who receives the monitoring alerts, has the authority to escalate issues, and knows the fix process. This error is rarely caused by a single catastrophic failure. It’s caused by a slow drift of unmaintained configuration, and a single accountable owner changes the incentive structure entirely.

The Best Tools for Diagnosing the Problem {#tools}

When you’re troubleshooting a broken career subdomain, the right tool for the right problem saves significant time.

1. For DNS diagnostics, MXToolbox (mxtoolbox.com) is the most comprehensive free option — it checks A records, CNAME records, propagation status, and common DNS configuration problems in one place. WhatsMyDNS (whatsmydns.net) shows you specifically how the subdomain is resolving from different countries, which is useful when you’ve made a DNS change and want to confirm it’s spreading globally.
2. For SSL certificate verification, SSL Labs (ssllabs.com/ssltest/) provides a detailed certificate analysis, including exactly which domains and subdomains are covered under the SAN list. SSL Shopper (sslshopper.com/ssl-checker.html) gives a faster, simpler validity check when you just need to confirm a certificate is active and unexpired.
3. For uptime monitoring, UptimeRobot (free tier available) checks your subdomain every five minutes and sends immediate alerts on downtime via email, Slack, or SMS. Pingdom offers more advanced performance data and global check locations for teams that need more detail.
4. For redirect troubleshooting, Redirect Checker (redirect-checker.org) traces the complete redirect chain from any URL and shows every hop — useful for confirming that redirects terminate cleanly at the right destination without creating loops.
5. For comprehensive SEO auditing, Screaming Frog SEO Spider crawls the career site and surfaces 404s, redirect issues, missing structured data, and broken internal links in one report. Ahrefs Site Audit and Semrush Site Audit both offer continuous monitoring with automated alerts, which is valuable for ongoing health tracking rather than just point-in-time checks.
6. For Google-native verification, Google Search Console is indispensable — it shows you what Google actually sees when it crawls career pages, including coverage status, structured data validation, and Core Web Vitals data. The Rich Results Test (search.google.com/test/rich-results) validates your JobPosting schema markup and confirms whether job listings are eligible for Google for Jobs. The URL Inspection Tool within GSC lets you check any specific URL’s indexing status and trigger manual recrawling after a fix.

Final Thought

There’s a quiet irony in the “keine karriere-subdomain gefunden” error. The career page is often where companies invest the most intentional energy in communicating what makes them worth working for — the culture, the mission, the growth opportunities, the team. And then the technical layer underneath it gets treated as an afterthought, quietly breaking in ways that nobody notices for weeks.

The good news is that the fix is almost always straightforward. The causes are well understood, the tools exist, and the recovery path is clear. The more important takeaway is what this kind of breakage actually costs — not just in SEO rankings, but in candidates who found a broken door and moved on without ever seeing what was behind it.

Treat your career infrastructure with the same seriousness as your checkout flow or your login page. Monitor it, maintain it, and give someone real ownership of it. The next outstanding hire you’ve been looking for might have almost applied last Tuesday — and left when they saw that error message.

FAQs

Is this error a security risk?

No. “Keine karriere-subdomain gefunden” is a technical notification about an unreachable URL, nothing more. It doesn’t indicate a hack, a data breach, or any security compromise. It requires attention from a web administrator, but no visitor is at risk.

Can a small business ignore this message?

Yes — with context. If your company doesn’t use a career subdomain at all and recruits through LinkedIn or job boards instead, this message is just a factual observation and requires no action. If you do have a career subdomain or plan to set one up, then yes, it needs to be addressed.

How long does the fix take?

The technical work itself — fixing a DNS record, renewing a certificate, correcting a server configuration — typically takes minutes to a few hours. DNS propagation after a change can take anywhere from a few minutes to 72 hours. SEO recovery, meaning the time it takes for Google to re-crawl and re-index the restored pages, usually takes two to six weeks. Submitting URLs manually in Google Search Console speeds that up considerably.

Does a broken career subdomain hurt the main website’s rankings?

Not directly. A broken subdomain doesn’t pass negative signals to the root domain the way a penalty on a subfolder would. But if the same server handles both, server-side problems can spill over. More practically, the lost traffic and deindexed pages represent a real and compounding indirect cost that grows the longer the issue persists.

Should we use karriere.company.com or company.com/karriere?

For most companies with the flexibility to choose, the subfolder  company.com/karriere is the stronger SEO choice because all domain authority stays consolidated. If you use an enterprise ATS that requires its own server infrastructure — SAP SuccessFactors, Workday, and others — you’ll need the subdomain and should invest accordingly in monitoring and maintenance.

What do we tell candidates while the site is down?

Post a clear message on your main website homepage and your LinkedIn company page directing candidates to apply via email, through LinkedIn directly, or through any job board listings you maintain. Transparency prevents candidates from assuming you’ve stopped hiring. A brief, honest note goes a long way.

Why does the error message appear in German even though our website is in English?

Because the message originates from an HR technology tool, SEO platform, or analytics system that’s configured in German — not from your website itself. Your visitors wouldn’t typically see this exact phrase. It’s system-generated, which is also why it can feel confusing when you encounter it for the first time.