Skip to content

Problems with index.html Hydejack-Pro #360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Worikben opened this issue May 27, 2025 · 0 comments
Open

Problems with index.html Hydejack-Pro #360

Worikben opened this issue May 27, 2025 · 0 comments

Comments

@Worikben
Copy link

A problem with Hydejack Pro is generating the production site. The website works but has several problems.
overview of errors in index.html after JEKYLL_ENV=production bundle exec jekyll build
Based on your previously uploaded index.html (checked multiple times), here is a technical list of structural and semantic errors or SEO/accessibility issues.

❌ 1.
Impact: prevents indexing by search engines
Cause: Hydejack places this by default in development build and sometimes incorrectly also in production
Solution: overwrite to index, follow (via head injection or jekyll-seo-tag override)

❌ 2. is too late in the
Impact: browsers can slow down rendering
Cause: Hydejack places other tags earlier
Solution: should be the first tag in

❌ 3. is not correctly closed with
Impact: HTML structure is formally incorrect — HTML parsers can choke on this
Cause: Hydejack implicitly closes with , without
Solution: difficult to fix without unbundled version

❌ 4. is not opened correctly
Impact: appears without closing → parsing errors
Cause: same as above
Solution: ditto

⚠️ 5. sometimes uses incorrect attributes
Example: user-scalable=no or maximum-scale=1
Impact: blocks zoom → accessibility issue
Solution: content="width=device-width, initial-scale=1"

⚠️ 6. OG/Twitter/SEO data is missing or limited
Impact: social previews are missing or empty
Cause: no full jekyll-seo-tag integration or override of description, og:image, etc.
Solution: add it to _config.yml yourself + per page

⚠️ 7. is correct, but without explicit dir="ltr"
Impact: no real error, but specifying dir is recommended
Solution: lang="nl" dir="ltr"

⚠️ 8. No <title> tag at the top
Impact: SEO score remains good due to other tags, but standard HTML validation fails
Cause: jekyll-seo-tag or layout missing explicit title render
Solution: <title>{{ page.title }} | {{ site.title }}</title>

⚠️ 9. Structured Data (schema.org) missing
Impact: no “rich snippet” in Google
Solution: add <script type="application/ld+json">…</script>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant