Generic selectors
Exact matches only
Search in title
Search in content
Search in posts
Search in pages

he point about headings is to have them in the right order. They are the structure that Google uses to make sure that it understands the post and what bits are important.

All posts must have Heading 1 and the next one should be heading 2.

Heading 1 must be the first one. You can change it’s size and colour if you want, it’s the code tag that matters which you needn’t even see.

The rest don’t matter so much but it’s best practice to have them in the right order if you are using several. However, sometimes you want a small header within a paragraph and that’s fine as long as you stick to the Heading 1 and 2 rule. This is what they look like in their raw state on this site:

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Paragraph text.

If you want to apply the main site colour to a text element, select the text you want to change colour of, use the colour dropdown, click custom and insert this hex code #01b7a8.

Do it like this:


Then you just copy in the hex code above (without the #). After you do the first one it will remain selectable for the rest of the post. T

On the code side, heading tags (and, actually, all style tags) close as soon as you hit return so that the next bit of text goes back to the default paragraph style. What this means is that, say you wanted to write a paragraph and have it all show up as Heading 5 style, and you hit return to make a new paragraph within that, it would revert to paragraph and you would need to select that next bit and apply Heading 5 to that as well. It can be a bit frustrating! What I generally do for an H5 paragraph is write the whole thing without breaks so it’s all H5, and then put the return breaks in afterwards and it usually sticks then. But it’s just as easy to just use the dropdown above and format each bit.