# search engine optimization Published articles for search engine optimization. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Optimizing Hugo Sitemaps to prioritize posts crawling over taxonomies DevFeed: [Optimizing Hugo Sitemaps to prioritize posts crawling over taxonomies]() Original publisher: [Read original article]() Author: Tom Published: 2024-05-17T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [Search engine optimization (SEO)](), [Protocol (disambiguation)]() Tags: [google](), [guide](), [hugo](), [hugo-changefreq-settings](), [hugo-site-seo](), [hugo-sitemap-optimization](), [robots](), [search](), [search-engine-optimization](), [search-engines](), [seo](), [seo-sitemap-tuning](), [sitemap-priority-settings](), [structure](), [taxonomy]() ### AI overview A practical guide to customizing Hugo sitemaps so posts receive higher crawl priority than taxonomy pages. It explains adjusting change frequency and priority while avoiding sitemap and breadcrumb issues that can appear in Google Search Console. ### Source excerpt Learn how to optimize your Hugo site's sitemap by adjusting priority and change frequency settings to improve SEO and guide search engine crawlers effectively. ## Automatically setting 'lastmod' in Hugo pages with Git modification date DevFeed: [Automatically setting 'lastmod' in Hugo pages with Git modification date]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-24T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [Git](), [Search engine optimization (SEO)](), [GitHub Actions](), [CI/CD](), [Cloudflare](), [WordPress]() Tags: [automatic-lastmod-setting](), [ci-cd](), [cloudflare](), [commit](), [configuration](), [devops](), [git](), [git-modification-date](), [github-actions](), [hugo](), [hugo-lastmod](), [hugo-seo-optimization](), [hugo-site-indexing](), [search-engine-optimization](), [seo](), [wordpress]() ### AI overview This tutorial explains how to set Hugo's lastmod parameter automatically from Git modification dates. It covers the need for full Git history, adjustments for GitHub Actions and Cloudflare Pages, and applicability to other CI/CD configurations. ### Source excerpt Learn how to automatically set the 'lastmod' parameter in Hugo pages using Git modification dates to improve SEO and expedite search engine indexing. ## The WebAssembly (Wasm) Content Management System (CMS) and Search Engine Optimization (SEO): A Short Story DevFeed: [The WebAssembly (Wasm) Content Management System (CMS) and Search Engine Optimization (SEO): A Short Story]() Original publisher: [Read original article]() Author: Tim McCallum Published: 2022-08-19T01:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly](), [Content Management System](), [Search engine optimization (SEO)](), [Web]() Tags: [cms](), [implementation](), [search-engine-optimization](), [using](), [wasm](), [webassembly]() ### AI overview A blog post explains how a user improved search-engine optimization for Bartholomew, Fermyon's WebAssembly-based content management system. ### Source excerpt This blog post shows you how to make a noticeable impact on the Web when using Fermyon's WebAssembly(Wasm) based Content Management System (CMS) called Bartholomew. The short story in this blog is about how a user made their Bartholomew CMS implementation better for search engines, through a process known as Search Engine Optimization (SEO). ## Making your website multi-regional using top-level domains DevFeed: [Making your website multi-regional using top-level domains]() Original publisher: [Read original article]() Author: Nicolas Mondollot Published: 2015-04-15T12:19:08Z Content type: article Language: en Sources: [eFounders]() Topics: [Website](), [Search engine optimization (SEO)](), [Rails](), [domain](), [Development]() Tags: [article](), [development](), [dns](), [domain](), [rails](), [search-engine-optimization](), [seo](), [startup](), [tech](), [website]() ### AI overview This article explains how to localize a website for multiple languages and regions, compare URL strategies for international SEO, and use country-specific top-level domains with Rails. It describes Drivy's choice of ccTLDs and notes limitations in a simple domain-based locale implementation. ### Source excerpt illustration: Adrien Griveau Hi there. My name is Nicolas Mondollot, I am the CTO of Drivy -- an awesome peer-to-peer car rental service. We launched our german website in early 2015. Here are some things we learned along the way. When you start a website you usually start small: one website, hosted on one domain, targeting one country and one language. Simple, right? Then, one day you decide to go international (exciting!). One problem, though: people don't all speak/read the same language everywhere. You must localize you content in multiple languages. The standardized way to do so is to use a locale for each language and geographical region you are targeting. For instance if you want to make your website available in the US, France and Canada you'll need 4 locales: en : English (US) fr : French (France) fr-CA : French (Canada) en-CA : English (Canada) side note: this is a 'pragmatic' approach to locale naming, where we drop the regional part when it is not needed (more information here). Great. Now, how do you make your website available in all these locales? Locales and URLs The first rule of Search Engine Optimization when you go international is: the locale must appear in the URL. Google suggests choosing among several options: URL parameters: example.com?locale=fr Subdirectories with a generic top-level domain (gTLD): example.com/fr/ Subdomains with a generic top-level domain (gTLD): fr.example.com Country-specific top-level domains (ccTLD): example.fr There is no one-size-fits-all approach. The best solution really depends on your specific requirements (this article from Moz may give you some pointers). At Drivy we decided to use ccTLDs because it was the best solution SEO-wise to target different countries. Plus it's prettier. First implementation In Rails this is pretty straightforward. You just need to point your new domain DNS to your application server and drop this code in your ApplicationController (inspired by the official Rails guide): class Applicat ## Alexa Toolbar and the Problem of Experiment Design DevFeed: [Alexa Toolbar and the Problem of Experiment Design]() Original publisher: [Read original article]() Published: 2007-01-08T00:00:00Z Content type: article Language: en Sources: [Peter Norvig]() Topics: [Statistics](), [Internet](), [trust](), [data](), [Search engine optimization (SEO)]() Tags: [alexa](), [amazon](), [bias](), [https](), [internet](), [logs](), [party](), [ranking](), [search-engine-optimization](), [seo](), [statistics](), [trust]() ### AI overview The article examines whether Alexa traffic rankings accurately represent internet usage. It argues that the rankings are affected by selection bias because they measure users who installed the Alexa toolbar, a group that may be disproportionately interested in SEO, and illustrates the concern with comparisons between site logs and Alexa rankings. ### Source excerpt Can you trust statistics about internet usage?