Job Indexing Health Check

Check page type, JobPosting schema, Google Indexing API publish/metadata, and Search Console URL Inspection — credentials stay in your browser session only.

Full Google check

Three steps — then run the full check. Nothing is stored on our servers.

  1. Add job URL

    Use a public single-job detail URL (https://).

    Schema + page type screening — no Google credentials needed.

  2. Connect to Google

    Sign in with the Google account that has Search Console access for this job site.

    Your privacy & security

    • Read-only access. We request Search Console permission to run URL Inspection only — not to change settings or collect analytics.
    • No password stored. Google handles sign-in; we never see or save your Google password.
    • Short-lived connection. OAuth tokens are kept in a temporary server cache for up to 60 minutes, tied to this browser session (~15 min). They expire automatically or when you click Disconnect.
    • Not saved to our database. Tokens are not written to site settings, user accounts, or permanent logs.
    • Used only for your check. We call Google’s API for the job URL you submit — we do not profile you or reuse access for marketing.
    Checking GSC connection…
  3. Add service account JSON

    What you need (Indexing API)

    • A Google Cloud project with the Web Search Indexing API enabled.
    • A service account in that project — create a key and download the JSON file.
    • The service account email added as an Owner on the job site in Google Search Console (required for publish/metadata to work).

    Your privacy & security

    • Never saved. Your JSON is pasted in the browser and sent over HTTPS only when you run a check. It is not stored in our WordPress database, files, or admin settings.
    • Session-only. The key exists only for this page visit. Reloading clears the textarea; closing the tab ends the session.
    • Your Google quota. API calls use your Cloud project limits — not SEOJobs’ credentials or billing.
    • Used only for your check. We use it to call Google’s Indexing API (publish and/or metadata) for the URL you entered — nothing else.
    • You stay in control. Use a dedicated service account if you prefer. Revoke or delete the key anytime in Google Cloud Console.

    Download from Cloud Console → IAM & Admin → Service accounts → Keys → Add key → JSON.

Both Google and service account credentials are session-only, auto-expire, and are never saved to the site database.