Fix json issue

[yurisasuke]

User description

For internal users - Please add a Jira DX PR ticket to the subject!

---

Preview Link

Description

Screenshots (if appropriate)

Checklist

• I have added a preview link to the PR description.
• I have reviewed the suggestions made by our AI (PR Agent) and updated them accordingly (spelling errors, rephrasing, etc.)
• I have reviewed the guidelines for contributing to this repository.
• I have read the technical guidelines for contributing to this repository.
• Make sure you have started your change off our latest master.
• For Tyk Members - Please add a Jira DX PR ticket to the subject!
• For Tyk Members - I have added the appropriate release label to this PR:
  • If it is for a future release, label it as future-release and specify the version (e.g., future-release, 6.0).
  • If it should be merged into an older version, use the specific version label (e.g., 4.1, 5.1).
  • If no label is added, it will be assumed that the PR should be merged into the latest current version (e.g., 5.5) and master.

---

PR Type

Enhancement, Bug fix

---

Description

• Updated JSON-LD structured data script for schema.org compliance.

• Added datePublished and dateModified fields for better metadata.

• Improved author and copyrightHolder fields with structured organization data.

• Fixed formatting and alignment issues in the JSON-LD script.

---

Changes walkthrough 📝

	Relevant files
Enhancement	site_schema.html Enhanced JSON-LD script with metadata and formatting fixes tyk-docs/themes/tykio/layouts/partials/site_schema.html Updated @context to use https://schema.org. Added datePublished and dateModified fields. Replaced plain text author and copyrightHolder with structured organization data. Improved formatting and alignment of JSON-LD script. +25/-12

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Possible Syntax Issue Ensure that the JSON structure is valid and correctly formatted, especially with the added keywords array and its conditional logic. {{ if isset .Params "tags" }} {{ range $index, $tag := .Params.tags }} "{{ $tag }}"{{ if ne $index (sub (len .Params.tags) 1) }},{{ end }} {{ end }} {{ end }} Date Format Consistency Verify that the datePublished and dateModified formats are correct and consistent with the expected ISO 8601 standard. "datePublished": "{{ .Date.Format "2025-02-26" }}", "dateModified": "{{ .Lastmod.Format "2006-02-26" }}"

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Use ISO 8601 format for dates Ensure that the dateModified field uses the correct date format to avoid potential parsing issues, as the format "2006-02-26" might not align with the expected ISO 8601 standard. tyk-docs/themes/tykio/layouts/partials/site_schema.html [30] -"dateModified": "{{ .Lastmod.Format "2006-02-26" }}" +"dateModified": "{{ .Lastmod.Format "2006-01-02T15:04:05Z07:00" }}" Suggestion importance[1-10]: 9 __ Why: The suggestion improves the date format to comply with the ISO 8601 standard, which is widely used and ensures compatibility with various systems. This change is highly relevant and impactful for maintaining proper data formatting.	High
General	Handle missing tags gracefully in JSON Validate that the keywords field properly handles cases where .Params.tags is not defined to avoid generating invalid JSON. tyk-docs/themes/tykio/layouts/partials/site_schema.html [22-27] "keywords": [ {{ if isset .Params "tags" }} {{ range $index, $tag := .Params.tags }} "{{ $tag }}"{{ if ne $index (sub (len .Params.tags) 1) }},{{ end }} {{ end }} + {{ else }} + "No tags available" {{ end }} ], Suggestion importance[1-10]: 8 __ Why: The suggestion addresses a potential issue where the keywords field could generate invalid JSON if .Params.tags is not defined. By adding a fallback, it ensures robustness and prevents errors, which is a significant improvement.	Medium

[netlify]

✅ PS. Pls add /docs/nightly to the end of url

Name	Link
🔨 Latest commit	c1e50c3
🔍 Latest deploy log	https://app.netlify.com/sites/tyk-docs/deploys/67c0052695d8df00082719c3
😎 Deploy Preview	https://deploy-preview-6035--tyk-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ PS. Pls add /docs/nightly to the end of url

Name	Link
🔨 Latest commit	8768ff1
🔍 Latest deploy log	https://app.netlify.com/sites/tyk-docs/deploys/67c006c7ef91b10008129bfc
😎 Deploy Preview	https://deploy-preview-6035--tyk-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[letzya]

@yurisasuke why?

[letzya]

Closing. dont think it's needed