Troubleshooting

A reference for diagnosing the most common issues you may encounter while operating your Cavuno job board. Each section follows the same structure: what you see, why it happens, and what to do about it.

Custom domain not connecting

A domain stays in "Pending" or "Awaiting DNS" status when Cavuno cannot verify the DNS records you configured at your registrar.

Diagnose

1. Open Board settings > Domains and compare the records shown against what you configured at your registrar. Values must match exactly.
2. Check whether you are connecting a subdomain (e.g., jobs.example.com) or a root domain (e.g., example.com). Subdomains require a CNAME record. Root domains require an A record.
3. Visit dnschecker.org and look up your domain. If the expected value appears for some regions but not others, propagation is still in progress. This can take up to 48 hours.
4. If you use Cloudflare, make sure the proxy status on your CNAME record is set to DNS only (grey cloud, not orange). Cloudflare's proxy intercepts traffic and prevents Cavuno from verifying ownership.
5. Click Verify on the Domains tab to trigger a fresh check. If all records are correct and propagated, the domain moves to "Active" and Cavuno provisions an SSL certificate automatically.

SSL certificate errors

After verification succeeds, SSL provisioning takes up to 15 minutes. If you see certificate warnings in the browser during this window, wait and try again. Clear your browser cache or test in an incognito window to rule out stale certificate data.

"Domain already in use" error

This domain is attached to another Cavuno board. If you own the domain and cannot add it, contact support so we can investigate.

Still not working?

If your domain has been pending for more than 48 hours with correct DNS records, contact support with your domain name and a screenshot of your DNS configuration.

Stripe payments not working

Employers see errors or the payment option does not appear on your board's job posting page.

Diagnose

1. Go to Board settings > Monetization and confirm your Stripe account shows a status of Complete. If it shows Incomplete, click through to finish Stripe's onboarding. Stripe requires identity verification and bank account details before you can accept live payments.
2. Verify you have at least one active pricing plan. Go to Board settings > Monetization and check the Pricing Plans section. Employers cannot pay if no plans exist.
3. Log in to your Stripe Dashboard and check whether the account is in test mode or live mode. Test mode payments do not process real charges and do not appear on your board for visitors.
4. In the Stripe Dashboard, go to Developers > Webhooks and confirm the Cavuno webhook endpoint is active and shows recent successful deliveries. Failed webhook deliveries mean Stripe processed the payment but Cavuno was not notified.
5. If an employer reports a specific failed charge, search for the payment in Stripe's Payments tab. The event log shows the exact reason for failure (declined card, insufficient funds, etc.).

Still not working?

If your Stripe status is "Complete" and plans are configured but payments still fail, contact support with the Stripe payment ID or error message.

Jobs not appearing in Google

Your job listings are published on your board but do not show up in Google search results or Google for Jobs.

Diagnose

1. Check how long ago the job was published. Google typically indexes new listings within 1-3 days. Boards with an established sitemap and crawl history get indexed faster.
2. Open Google's Rich Results Test and paste the URL of a specific job page. Verify that JobPosting structured data is detected without errors. Cavuno generates this schema automatically, but missing fields (especially validThrough, the expiry date) can prevent inclusion.
3. In Google Search Console, go to Enhancements > Job postings. Review errors and warnings. Common issues include expired jobs still in the index, missing salary data (optional but recommended), or invalid location formats.
4. Submit your sitemap at yourboard.com/sitemap.xml in Search Console under Sitemaps if you have not done so already. Cavuno generates the sitemap automatically.
5. Ensure job titles are descriptive and standard. Google deprioritizes listings with vague titles like "Amazing Opportunity" or internal codes like "REQ-4521". Use clear titles such as "Senior Software Engineer" or "Marketing Manager".

Improving visibility in Google for Jobs

• Add salary ranges when possible. Google surfaces these listings more prominently.
• Set realistic expiry dates (30-60 days). Avoid years-long expiry windows.
• Include complete location data (city, state/region, country) or clearly mark jobs as "Remote".
• Write substantive descriptions with at least 100 words covering responsibilities and requirements.

Still not working?

If jobs have been live for more than a week with valid structured data and no Search Console errors, contact support with the job page URL and a screenshot of the Rich Results Test output.

Job alerts not being received

Subscribers report they are not receiving job alert emails, or alert delivery seems inconsistent.

Diagnose

1. Confirm the subscriber's status is Active in your subscriber list. Go to Job Alerts in the sidebar and search for their email address. If their status is "Unsubscribed" or "Unconfirmed", they will not receive alerts.
2. Ask the subscriber to check their spam, junk, and promotions folders. Many email providers automatically filter automated emails from unfamiliar senders.
3. Verify that job alerts are enabled for your board. Go to Board settings and confirm the job alerts toggle is on.
4. Check whether new jobs actually match the subscriber's alert criteria. The system only sends alerts when jobs match the subscriber's keyword, location, and type preferences. If no jobs match, no email is sent for that period.
5. Ask the subscriber to add your board's sending address to their contacts or safe sender list. This prevents future filtering.

Confirmation emails not arriving

New subscribers must click a confirmation link before they receive alerts. If the confirmation email does not arrive, the same spam-filter guidance applies. The subscriber can re-enter their email on the subscribe form to trigger a new confirmation email.

Still not working?

If a confirmed, active subscriber with matching job criteria is not receiving alerts, contact support with the subscriber's email address and the approximate date they last expected an alert.

Backfill not importing jobs

You have configured backfill rules or enabled company backfilling, but no jobs are appearing on your board.

Diagnose

1. Go to Board settings > Backfill and verify you have at least one active rule, or at least one company enabled under the Backfilling tab.
2. Review your rule match conditions. If conditions are too narrow (e.g., requiring all terms to match simultaneously, or using very specific titles), few or no jobs will qualify. Broaden the terms or switch from "match all" to "match any".
3. Check your filters. Country, seniority, employment type, and workplace type filters all reduce the pool of eligible jobs. Remove or widen filters temporarily to confirm jobs start flowing.
4. Under the Companies section, click the Backfill Supported tab. Only companies with a valid, accessible careers page can be backfilled. If a company appears under Not Backfilling, their careers page may be unavailable or unsupported.
5. Backfill runs on regular sync cycles. After making changes, wait for the next cycle to complete. New jobs typically appear within a few hours.

Wrong jobs appearing

If irrelevant jobs are imported, add exclude terms to your rules, tighten your filters, or update the validation description under the rule settings cog icon. The validation description helps AI determine which jobs belong on your board.

Still not working?

If rules and companies are configured correctly and no jobs appear after 24 hours, contact support with your board name and a description of the rules you have set up.

Analytics not tracking visitors

Your Cavuno dashboard or Google Analytics shows zero or unexpectedly low visitor counts.

Diagnose

1. Confirm your GA4 Measurement ID starts with G- (not UA-, which is the deprecated Universal Analytics format). Go to Board settings > Analytics and check the value.
2. Visit your job board in a regular browser window, then open Google Analytics and go to Reports > Realtime. If your visit appears, tracking is working. Standard reports can take up to 24 hours to populate.
3. If you have enabled Require cookie consent in Board settings > Analytics, tracking only starts after a visitor accepts cookies. This is expected behavior for GDPR compliance, and it means reported traffic will be lower than actual traffic.
4. Test in a browser without ad blockers or privacy extensions. Tools like uBlock Origin, Privacy Badger, and Brave's built-in shield block analytics scripts. This affects all analytics platforms, not just Cavuno.
5. For the built-in Cavuno dashboard analytics, no additional configuration is needed. If the dashboard shows data but Google Analytics does not, the issue is isolated to the GA4 configuration.

Google Tag Manager not firing

If you use GTM instead of GA4 directly, confirm your Container ID starts with GTM- and is saved in Board settings > Analytics. Then verify your GTM container has been published (unpublished containers do not fire tags).

Still not working?

If your Measurement ID is correct and you see your own visit in the Realtime report but historical data never appears, contact support with your Measurement ID and board URL.

Website changes not appearing

You updated content, settings, or design in the Cavuno dashboard but your live board still shows the old version.

Diagnose

1. Do a hard refresh in your browser: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac). Browsers aggressively cache pages, stylesheets, and images.
2. Open an incognito or private browsing window and visit your board. If the changes appear there, your regular browser is serving a cached version. Clear your browser cache to resolve it.
3. Changes propagate through the CDN within a few minutes of saving. If you made the change less than five minutes ago, wait and check again.
4. If you changed your custom domain or subdomain settings, cache invalidation covers multiple layers (DNS, CDN, application). Domain-related changes may take slightly longer to fully propagate.
5. Check whether the change was actually saved. Return to the relevant settings page in the Cavuno dashboard and confirm the new values are present.

Still not working?

If changes are saved in the dashboard, you have cleared your cache, and the old content persists after 15 minutes, contact support with your board URL and a description of the change you made.