Overview
This article helps you understand and implement structured data in Access Volcanic. Structured data is a standardised format that helps search engines understand your job postings and content pages, improving their chances of appearing in enhanced search features like Google for Jobs. You'll learn how to enable structured data, edit schemas for specific pages and jobs, and troubleshoot common visibility issues.
Key benefits
Improve search engine visibility by helping Google understand your content more accurately.
Make your job postings eligible for Google for Jobs listings and rich search results.
Generate automatic structured data for both jobs and CMS pages across your website.
Enhance user experience by making your content easier to find in search results.
Support future SEO requirements with standardised data formatting.
Add site-wide schemas for consistent business information across all pages.
Before you start
Before implementing structured data, make sure you have:
Admin Area access to your Access Volcanic platform.
A clear understanding of which content you want to prioritise for search engines.
Basic knowledge of JSON-LD (JavaScript Object Notation for Linked Data) format if you plan to make custom edits.
Access to Google Search Console for monitoring and validation or monitoring and validation.
📌 Note: Structured data makes your content eligible for enhanced search features but doesn't guarantee inclusion in Google for Jobs or rich results.
Understanding structured data
Structured data is a standardised format (usually JSON-LD) that provides additional context about your web page content. Search engines use this information to better understand what your pages contain and how to display them in search results.
Access Volcanic automatically generates structured data for jobs using JobPosting schema, which makes them eligible for Google for Jobs. The platform also supports structured data for CMS pages and allows you to add custom site-wide schemas when needed.
Enabling structured data for pages
Accessing structured data settings
Log in to your Admin Area.
Select the Your Website tab.
Under SEO Area, click Structured Data.
If Structured Data is disabled, toggle the Off button to On to enable the feature.
📌 Note: This section shows an overview of structured data fields and enables the feature, but doesn't allow direct editing. To edit structured data, follow the steps in the sections below.
Once enabled, you'll see a Structured Data button when editing both jobs and pages, allowing you to view and customise the generated schemas.
Editing structured data for pages
Page structured data enhances search visibility for your website pages. For pages, structured data automatically includes page title, sub-banner content, date published, and date modified.
📌 Note: The @type and headline fields are auto-populated by default, but you can edit these areas if preferred.
Editing page structured data
Navigate to the custom page you want to edit.
Click Edit then select Structured Data.
Configure the @type (choose from Article, NewsArticle, or BlogPosting).
Add your headline in the free text field.
For additional schemas, add code to the Additional header code section.
Check Do not include the above script in header code if you don't want the additional code included.
Click Submit to save changes.
⚠️ Important: Ensure any changes remain valid JSON-LD format and follow appropriate schema.org types like Article or WebPage. Only add properties that accurately represent content actually present on your page.
Optimising job structured data
Google for Jobs optimisation
Job structured data is built with Google for Jobs in mind, making it automatically compatible with Google's requirements. Access Volcanic automatically generates JobPosting structured data for all jobs. For high-priority positions, you can use Google for Jobs Optimisation to enhance the schema with additional details.
Editing job structured data
Log in to your Admin Area.
On the top right, click Structured Data.
Edit job-specific schema fields for Google for Jobs compatibility.
Click Submit once changes are completed.
📌 Note: These fields are taken from Google's structured data requirements and matched to the relevant Access Volcanic job fields.
Editable fields
The following fields can be customised for enhanced Google for Jobs compatibility:
Field | Input Type | Description |
title | Free text | The job title - should be clear and concise, accurately reflecting the role |
validThrough | Date picker | The date after which the job posting will expire |
employmentType | Dropdown menu: FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, VOLUNTEER, PER_DIEM, OTHER | The nature of the job (full-time, part-time, contract, etc.) |
hiringOrganization |
| Company information |
↳ name | Free text | Name of the hiring company or organisation |
↳ sameAs | Free text | URL of the company's official website or profile |
baseSalary |
| Salary information |
↳ currency | Free text | Currency code (e.g., GBP, USD, EUR) |
↳ unitText | Dropdown menu: HOUR, DAY, WEEK, MONTH, YEAR | How often the salary amount is paid |
↳ minValue | Free text | Minimum salary amount |
↳ maxValue | Free text | Maximum salary amount |
jobLocation |
| Job location details |
↳ streetAddress | Free text | Street address of the job location |
↳ addressLocality | Free text | City or town where the job is located |
↳ addressRegion | Free text | County, state, or region |
↳ postalCode | Free text | Postcode or ZIP code |
↳ name | Free text | Location name or building name |
🤓 Tip: Apply optimisation selectively to strategic roles rather than trying to enhance every job posting manually.
Employment type mapping
Administrators and SEO specialists should configure job types to match Google's expected employment type values. This mapping ensures your job categories align with Google's recognised standards for better Google for Jobs compatibility.
Google Employment Type
Type | Description |
FULL_TIME | Full-time positions |
PART_TIME | Part-time positions |
CONTRACTOR | Contractor positions |
TEMPORARY | Temporary positions |
INTERN | Internship positions |
VOLUNTEER | Volunteer positions |
PER_DIEM | Positions paid by the day |
OTHER | Different position types not covered above |
Navigate to your job type settings and use the Google for Jobs employment types field. Map each of your internal job categories to the appropriate Google value. This configuration affects how your jobs appear in Google for Jobs search results.
Google for Jobs compatibility
Job structured data is formatted to meet Google for Jobs standards. When Google crawls your website, it can discover and display your job postings in Google's job search results if the data meets their requirements.
Logo requirements
Ensure your logo meets Google's requirements:
Square format, minimum 112 x 112 pixels.
File named logo (e.g., logo.png).
File type: .jpg, .png, or .gif format.
📌 Note: Google doesn't guarantee that structured data will appear in search results, even when properly marked up. Results depend on Google's algorithms and policies.
Adding site-wide schemas
For organisation information or navigation schemas that should appear on every page, you can add global structured data to your site templates.
Prepare the JSON-LD schema code for site-wide use.
Add the schema script to your site's Page Tags section.
Validate the schema using Google's Rich Results Test.
Ensure the global schema doesn't conflict with existing page-specific structured data.
⚠️ Important: Global schemas affect your entire website. Review changes with an SEO specialist if you're unsure about implementation.
Best practices
Keep job and page content complete and accurate to support the structured data schemas.
Use optimisation features selectively on high-priority jobs rather than applying them broadly across all postings.
Validate structured data regularly using Google's Rich Results Test tool to identify and resolve issues promptly.
Monitor performance through Google Search Console, tracking impressions, clicks, and indexing status for job and page URLs.
Focus on documented, relevant schema types rather than experimental implementations.
Avoid adding unnecessary schema types that could confuse search engines.
Review and update structured data after major website changes or template modifications to maintain compatibility.
📌 Note: Quality over quantity - well-implemented structured data on key pages performs better than widespread but poorly configured schemas.
FAQs
Q1: Does adding structured data guarantee my jobs will appear in Google for Jobs?
Answer: No, structured data makes your jobs eligible for Google for Jobs but doesn't guarantee inclusion. Google controls indexing and visibility based on their own ranking processes and quality guidelines.
Q2: Can I optimise structured data for all my jobs at once?
Answer: Google for Jobs Optimisation is designed for individual jobs, not bulk application. Focus on strategically important positions rather than trying to enhance every job posting.
Q3: Should I be concerned about structured data warnings in Google's testing tools?
Answer: Address errors where possible, but warnings for optional fields don't prevent indexing. Focus on fixing required field errors and validation issues that could impact functionality.
Q4: Can global schemas conflict with page-specific structured data?
Answer: Yes, global and page-specific schemas can conflict if they duplicate the same schema types. For example, if you add Organisation schema globally and also include Organisation schema on individual pages, search engines may receive conflicting information about your business details. Ensure global schemas complement rather than contradict individual page markup.
Q5: How often should I check my structured data?
Answer: Review structured data after major website changes, template updates, or job configuration modifications. Regular monitoring in Google Search Console helps identify issues early.
Q6: What should I do if Google applies a manual action to my site?
Answer: Check the Manual Actions section in Google Search Console, resolve any highlighted issues quickly, and request a review once problems are fixed. Manual actions can suppress job visibility.
Q7: My jobs aren't appearing in Google for Jobs. How do I check if my structured data is correct?
Answer: Copy the URL of your job page, open Google's Rich Results Test tool, paste the URL and run the test. Review any warnings or errors reported for the JobPosting schema, correct issues in your CMS, and re-test until validation passes.
Q8: My structured data is valid but my jobs still aren't being indexed. What should I do?
Answer: Check indexing status in Google Search Console, submit your XML sitemap to help Google discover your pages, consider submitting a dedicated job sitemap for faster indexing, and monitor indexing progress over time in Search Console.
Q9: How can I ensure my job postings comply with Google's content guidelines?
Answer: Include detailed and accurate job descriptions, avoid publishing duplicate jobs with minor variations, remove or redirect expired job URLs to prevent dead links, and maintain unique content across your job postings. Set up redirects from expired job URLs to relevant pages like your job search results to maintain SEO value.
Q10: Why might my "Apply via Site" button not appear in Google for Jobs?
Answer: Google prioritises apply options based on job uniqueness, site authority, and source reliability. Google identifies your site as the primary job source based on how unique your job content is compared to other platforms and the strength of your site's authority. To improve visibility, maintain unique job descriptions and high-quality structured data that establishes your site as the authoritative source.
Q11: I can see the structured data overview but can't edit anything. What should I do?
Answer: The structured data overview section under SEO Area shows field summaries and enables the feature, but doesn't allow direct editing. To edit structured data, navigate to individual pages or jobs and click the Structured Data button on their edit screens.