A Page Per Course, Built to Book

Answering the four questions the visitor came with, above the fold, in the order they think of them. Is this the right certification for what my employer asked for. How long will it take. When is the next class. What does it cost. Every one of those has a specific answer and none of them require a paragraph. Then put the booking calendar on the same page, because a Contact Us button asks someone who was ready to buy to instead start a conversation and wait. Design matters far less than most people believe. A plain page that answers the four questions and lets her book beats a beautiful page that makes her hunt.

One page per course, and per format where the format changes the buying decision. A student searching BLS renewal has a different need from one searching HeartCode BLS, and a page trying to serve both serves neither well. It cannot match the search phrase in its title, it cannot answer the specific question in its first paragraph, and it makes the reader do the filtering. Splitting them also gives you somewhere real to put each course's FAQ, schedule, and structured data. The objection is always maintenance, and that is a real cost right up until the pages pull their content and pricing from one source instead of being hand-edited copies.

Yes, if they are actually different pages. A city page earns its place when it contains something true only about that city: where you train, which employers and facilities are nearby, how far you travel, what the drive is like. A page that is the same text with the city name swapped in is obvious to a reader in about four seconds and adds nothing to your site. The way to know you have built a real one is whether a local reading it learns something. We run city pages for the San Gabriel Valley cities we serve, and the ones that work are the ones with specifics in them.

Inventory first, redirect completely, then verify. Before touching anything, list every live URL and what it ranks for. Every one of those either survives at the same path or gets a permanent redirect to its closest equivalent, and closest means the same intent rather than the homepage. Redirecting everything to the homepage is the classic way to lose traffic during a migration. Keep titles and canonical URLs deliberate rather than autogenerated, and check the sitemap against your inventory after launch. We moved our own site across 89 pages, which is small enough to hand-check and large enough that a missed redirect would have shown up in traffic within a week.

An H1 that matches the search phrase a real person types, not a slogan. An opening paragraph that answers the primary question in the first two sentences, because that is what gets pulled into a search snippet. H2s phrased as the actual follow-up questions: how long is the class, is this the card my employer accepts, how much does it cost. A visible FAQ with FAQPage markup, so those questions can appear directly in results. Course and breadcrumb structured data so the page's place in the site is explicit. And internal links to the neighbouring courses, since the visitor who wanted BLS sometimes needs ACLS instead.