97th Floor SEO optimization #2376
Conversation
@cnunciato optimized for KW: CloudFormation. I'm not sure how to create headers, but "What is Pulumi?", "What is CloudFormation?" and "The Pulumi Difference" were intended to be subheadings. If that's not possible they're also fine as they are.
| title: Pulumi vs. Cloud Templates (AWS CloudFormation, etc.) | ||
| meta_desc: This page gives an overview of the major differences between Pulumi | ||
| and Cloud Templates (AWS CloudFormation, etc.). | ||
| title: Pulumi vs. AWS CloudFormation and Other Templates | Pulumi |
There was a problem hiding this comment.
A while ago, we used to auto-append "| Pulumi" to all page titles. Is that worth bringing back?
There was a problem hiding this comment.
There's room for adjusting to suit your brand, as it's not a super important SEO issue, but Moz does recommend the "| Brand Name" format for title tags in Google; it looks good and keeps things uniform, so that's what we typically recommend.
There was a problem hiding this comment.
In most cases (including this page), we do indeed append this automatically, yep:
https://github.com/pulumi/docs/blob/master/layouts/partials/head.html#L66-L71
(So there's no need to specify these manually in frontmatter titles, @97thFloor.)
| @@ -42,5 +49,5 @@ There are many community-led projects which allow you to write code in a real la | |||
| configuration templates as a sort of "compilation" step. These offer nice syntactic sugar on top of the raw | |||
| templates, but the underlying model leaks through and carries forward all of the other abovementioned shortcomings. | |||
|
|
|||
| Finally, Pulumi is [open source](https://github.com/pulumi/pulumi) and community-driven. All of the cloud systems are | |||
| Finally, Pulumi is [open source](https://github.com/pulumi/pulumi) and community-driven. All of the other cloud systems — such as Azure Automation or AWS CloudFormation — are | |||
There was a problem hiding this comment.
| Finally, Pulumi is [open source](https://github.com/pulumi/pulumi) and community-driven. All of the other cloud systems — such as Azure Automation or AWS CloudFormation — are | |
| Finally, Pulumi is [open source](https://github.com/pulumi/pulumi) and community-driven. All of the other cloud systems — such as Azure Resource Manager or AWS CloudFormation — are |
| title: Pulumi vs. Cloud Templates (AWS CloudFormation, etc.) | ||
| meta_desc: This page gives an overview of the major differences between Pulumi | ||
| and Cloud Templates (AWS CloudFormation, etc.). | ||
| title: Pulumi vs. AWS CloudFormation and Other Templates | Pulumi |
There was a problem hiding this comment.
| title: Pulumi vs. AWS CloudFormation and Other Templates | Pulumi | |
| title: Pulumi vs. AWS CloudFormation and Other Templates |
| @@ -11,18 +10,26 @@ menu: | |||
| aliases: ["/docs/reference/vs/cloud_templates/"] | |||
| --- | |||
|
|
|||
| What is Pulumi? | |||
|
|
|||
| Pulumi offers a multi-cloud alternative to typical, more restrictive infrastructure-as-code template solutions, such as AWS CloudFormation. Pulumi allows you to streamline processes through managing resources from different platforms all in one place, using real code, in your favorite language. | |||
There was a problem hiding this comment.
| Pulumi offers a multi-cloud alternative to typical, more restrictive infrastructure-as-code template solutions, such as AWS CloudFormation. Pulumi allows you to streamline processes through managing resources from different platforms all in one place, using real code, in your favorite language. | |
| Pulumi offers a multi-cloud alternative to more restrictive infrastructure-as-code template solutions, such as AWS CloudFormation. Pulumi allows you to streamline processes through managing resources from different platforms all in one place, using real code, in your favorite language. |
| Pulumi's model shares a lot with these systems. Although Pulumi programs are written in imperative, familiar languages, | ||
| they are ultimately evaluated to produce a similar set of create, update, or delete operations for your cloud resources. | ||
|
|
||
| This is where Pulumi begins to diverge from these other solutions, however. | ||
| This is where Pulumi begins to diverge from these other solutions such as AWS CloudFormation, however. |
There was a problem hiding this comment.
This feels stuck in, here. The sentence as a whole doesn't work with it.
There was a problem hiding this comment.
Maybe "This is where Pulumi begins to diverge from solutions like AWS CloudFormation, however"?
|
|
||
| Pulumi lets you use your favorite languages, instead of bespoke templating solutions. These typically use syntaxes that | ||
| Pulumi lets you use your favorite languages — complete control rather than bespoke templating solutions such as CloudFormation. These templates typically use syntaxes that |
There was a problem hiding this comment.
This sentence is no longer clear. Should the dash be a colon? And "complete control" and "bespoke templating solutions" are not directly comparable enough to be separated with a "rather than". (In other words, languages and templating solutions are comparable, as they're both technologies. Control is not a technology.)
There was a problem hiding this comment.
It's probably fine to leave as is then, as long as we can still get the "CloudFormation" part in there.
| meta_desc: This page gives an overview of the major differences between Pulumi | ||
| and Cloud Templates (AWS CloudFormation, etc.). | ||
| title: Pulumi vs. AWS CloudFormation and Other Templates | Pulumi | ||
| meta_desc: This page gives an overview of the major differences between Pulumi and Cloud Templates such as AWS CloudFormation. |
There was a problem hiding this comment.
Caps are unnecessary, as cloud templates isn't a proper noun.
| meta_desc: This page gives an overview of the major differences between Pulumi and Cloud Templates such as AWS CloudFormation. | |
| meta_desc: This page gives an overview of the major differences between Pulumi and cloud templates such as AWS CloudFormation. |
| @@ -11,18 +10,26 @@ menu: | |||
| aliases: ["/docs/reference/vs/cloud_templates/"] | |||
| --- | |||
|
|
|||
| What is Pulumi? | |||
There was a problem hiding this comment.
Leading off with what sounds like an ad for Pulumi doesn't seem like the right thing, here, since these pages are aimed at delivering comparative info, and they'd seem to be working relatively well in that regard. I'd remove these headings and this introductory section and leave these pages structurally as they are today, unless breaking them up is solving a problem that can't be solved otherwise.
There was a problem hiding this comment.
It was mostly to get the "What is CloudFormation?" part in there, as that is the first snippet question on the SERP, and CloudFormation is the primary KW. The "What is Pulumi?" part was more to balance it out and provide a clearer structure, since this is a comparison page. Would it be ok to switch the order and lead with CloudFormation?
|
This PR is now being tracked in #2515. Closing. |
@cnunciato this was optimized for KW: CloudFormation. I realized I made the changes, but not a pull request.
Proposed changes
Instances of keyword added, as well as relevant language to aid ranking, based on semantic analysis of SERP.
I'm not sure how to create headers, but "What is Pulumi?", "What is CloudFormation?" and "The Pulumi Difference" were intended to be subheadings. If that's not possible they're also fine as they are.