Many blogs “write a lot,” but their search exposure never increases. Usually, the content isn’t entirely bad, but the technical foundation is lacking. This article gives you an SEO technical checklist tailored for Jekyll sites, aiming to achieve “crawlable, understandable, and indexable” first.
1. Crawling and Indexing Basics
First, confirm three things:
robots.txtis accessible and the rules are correct.sitemap.xmlis accessible and contains article URLs.- Article pages do not contain mistakenly set
noindextags.
Minimum check command:
curl -I https://your-domain.com/robots.txtcurl -I https://your-domain.com/sitemap.xml2. Unified Canonical Rules
Jekyll can easily generate duplicate URLs due to pagination, category pages, or parameter links. It is recommended that every article outputs a canonical tag pointing to its unique official address.
Example (placed in <head>):
<link rel="canonical" href="{{ site.url }}{{ page.url | replace:'index.html','' }}">3. Structured Data (JSON-LD)
Add BlogPosting structured data to article pages to help search engines understand the content type and author information.
Critical fields should include at least:
headlinedatePublisheddateModifiedauthormainEntityOfPage
If you have a cover image, adding the image field yields better results.
4. Information Architecture: Hub Pages Must Have Value
Many sites’ tag/archive pages are just a list of links, making the content too thin. Suggestions:
- Add topic descriptions to each hub page.
- Write introductory paragraphs for key categories.
- Create “Beginner entry” and “Advanced entry” sections within the hub page.
This not only improves user experience but also reduces “thin content page” signals.
5. Internal Linking Strategy
Every technical article should have at least two types of internal links:
- Horizontal links: Related articles under the same topic.
- Vertical links: Prerequisite knowledge and advanced tutorials.
Rule: Internal links must serve the reading path, not just exist to make up numbers.
6. Metadata and Readable Titles
Pre-publish check:
titleis not clickbait; contains explicit topic keywords.subtitlesupplements the scenario and benefits.tagsare consistent with the body; avoid overly broad tags.- The first paragraph (80-120 words) clearly states “what this article helps you solve.”
7. Performance and SEO Synergy
Technical SEO isn’t just about tags; page experience also affects the results.
Priority optimization suggestions:
- Above-the-fold image size.
- Render-blocking JS/CSS.
- Mobile readability.
8. Post-Publish Verification Process
- Local
bundle exec jekyll buildto confirm build success. - Manually check the status codes of critical pages after going live.
- Submit the sitemap in Search Console.
- Observe exposure and index changes over 2-4 weeks.
Summary
For a personal blog, the first step in SEO is not “researching dark magic,” but completing the technical baseline. When crawling, structure, and experience all meet the standards, the value of high-quality content will be amplified much more stably.
If this article helped you, please share it with others!
Some information may be outdated