# Blocks Specifics

## HTML Tag

`HTML tags` are like keywords which define how the web browser will format, display and understand the content.

These tags basically highlight portions of your content for a search engine. They are not necessary, but considerably improve the SEO value of your web page.

<details>

<summary>Apply</summary>

1. Select a block
2. Open the Block Inspector
3. Navigate to the Primary tab
4. Select the appropriate tag from the HTML Tag field

</details>

### Available HTML tags

Cwicly allows you to use various HTML5 semantic tags for your blocks and content.&#x20;

***\<div>*** (division tag) Most general and useable tag in web development. If the block you are working on doesn't have a specific semantic tag that can be attached to it, it is best to use the **div** tag.

***\<header>*** Isolates the top part of the web page. It generally contains a logo and a navigation menu.

***\<footer>*** isolates the bottom part of the web page. It generally contains meta information.

***\<main>*** represents the *main* topic or core content of the web page. A web page should only contain one unique \<main> element.

***\<article>*** isolates a post from the rest of the code, makes it portable. It implies the content is independent and self-contained (e.g. blog post).&#x20;

***\<section>*** isolates content inside a group (i.e. the content relates to a single theme), and should appear as an entry in an outline of the page.

***\<aside>*** isolates supplementary content that is not part of the main content.

***\<nav>*** isolates navigation menus, groups of navigational elements. It is only to be used for important navigation blocks.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cwicly.com/miscellaneous/blocks-specifics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.