HTML Interview Questions: SEO, Performance and Tooling
Twenty five questions on the parts of front end work that touch the business directly, and where a markup answer is expected rather than a marketing o...
Making pages findable and understandable to search engines.
25 notes tagged
Twenty five questions on the parts of front end work that touch the business directly, and where a markup answer is expected rather than a marketing o...
The final build. Everything in the path applied to one real site, with a defined standard it has to meet before it is finished.
Filters, sorting, pagination and a product grid. The page where canonical tags, crawl budget and accessible dynamic updates all become real problems.
Six pages sharing a layout, with consistent navigation, breadcrumbs, a sitemap and metadata that differs correctly on every page.
Long form content done properly: article structure, a table of contents, figures, code blocks, an author footer and Article structured data.
Everything worth verifying before a page goes live, grouped so it can be worked through in about twenty minutes.
What the markup alone can do for speed, with no build tooling: resource hints, image discipline, script loading and the small set of attributes that m...
Three measurements taken from real visits, and one indexing rule that decides which version of your page Google actually reads.
Machine readable facts about your page, using a shared vocabulary. It does not raise rankings, and it can change how your result looks entirely.
The same page reachable at seven URLs is seven competing pages to a search engine. One line of markup consolidates them.
Two files at the root of your site that decide what gets crawled and what gets found. Small, easy to write, and easy to break in ways that remove a wh...