# Identify pages

## How the page is identified

In order to know what creative it needs to display, the SDK *(→ sdk)* will resolve the page URL by taking the first available value between the following:

* `<meta property="og:url" content="CANONICAL_URL">`
* `<link rel="canonical" href="CANONICAL_URL">`
* the current location

## If your URLs can change

In the newsroom, you might want to make a Collective Audience™ creative to go along with your article, and you might want to prepare it before you have a definitive URL (e.g. clicking the `Add Content` button on your draft page).

Given the URL registered at first is the one from the draft, the content wouldn't appear on the definitive page. That's why we offer a way to provide the **internal ID** of the page (e.g. the wordpress [`the_ID()`](https://developer.wordpress.org/reference/functions/the_id/)).

Just add the following meta, replacing `YOUR_INTERNAL_ARTICLE_ID` with the internal unique ID of your page.

```markup
<meta name="beop:id" content="YOUR_INTERNAL_ARTICLE_ID" />
```

## Page keywords

Page keywords can be useful when using the "broaden diffusion" feature.

By default, Collective Audience™ will read the keywords `meta` from your page.

Nevertheless, you can override it by setting a JavaScript variable containing an array of strings (the keywords) **before** the Collective Audience™ SDK initialisation.

```javascript
window.beOpKeywords = ["keyword1", "keyword2"];
```