How to Fix ‘The Following Required Properties Are Missing: fb:app_id’

Understand the fb:app_id warning, decide whether your site needs a Meta App ID, and fix the Open Graph metadata without using a fake or borrowed ID.

Primary keyword: the following required properties are missing: fb:app_idUpdated 2026-07-18

How to Fix ‘The Following Required Properties Are Missing: fb:app_id’ help workflow shown on a phone and laptop — Independent guide. No Facebook login required.

Quick answer

The message “The following required properties are missing: fb:app_id” usually comes from a social-sharing validator. It means the page does not identify a Meta app that owns or manages the URL's Facebook-specific integration.

Do not paste a random App ID just to make the warning disappear. First confirm that your page has the four basic Open Graph properties: og:title, og:type, og:image, and og:url. Then add fb:app_id only if the website has a Meta app and you control that app.

The warning is often separate from the reason a link preview is missing its title, description, or image. A bad og:image URL, blocked crawler, client-only metadata, redirect, or stale cache can break a preview even when fb:app_id is present.

What fb:app_id means

fb:app_id is a Facebook-specific meta property. Its value is the numeric ID of a Meta app created for a website or integration. It can associate shared URLs with that app and may be relevant to app-level tools or insights.

It is not one of the Open Graph protocol's four basic required properties. The Open Graph protocol lists og:title, og:type, og:image, and og:url as the core set. This distinction matters: a validator can call fb:app_id “required” for a Meta-specific feature while the page still has valid basic Open Graph markup.

Decide whether you should add it

Add fb:app_id when all of the following are true:

Your organization has a Meta app for the website or product.
You can access that app in Meta's developer dashboard.
The website's domain and app configuration are maintained by the same organization.
You have a real reason to connect shared URLs to the app.

If you publish a normal blog or informational site and do not use a Meta app, focus first on correct Open Graph tags and a working share image. Leaving an ownership warning unresolved is better than claiming another developer's app.

Add the tag correctly

Place the tag in the server-rendered <head> of the page:

<meta property="fb:app_id" content="YOUR_NUMERIC_META_APP_ID" />

Replace the placeholder with an App ID you control. Do not include spaces, a secret key, an access token, or the app's display name. An App ID is not the same as an App Secret; the secret must never be exposed in HTML.

A practical minimum set of sharing metadata looks like this:

<meta property="og:title" content="A clear page title" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://example.com/guide/" />
<meta property="og:image" content="https://example.com/images/guide.jpg" />
<meta property="og:image:alt" content="A useful description of the image" />
<meta property="og:description" content="A concise summary of the page" />
<meta property="fb:app_id" content="YOUR_NUMERIC_META_APP_ID" />

og:description and og:image:alt are not part of the basic four, but they improve context and accessibility. Use absolute HTTPS URLs for the canonical URL and image.

Verify what the crawler can see

Open the public page in a private browser window and confirm it does not require a login.
View the delivered HTML source, not only the browser's live DOM after JavaScript runs.
Search the source for og:title, og:url, og:image, and fb:app_id if you added it.
Open the og:image URL directly and confirm it returns an image without a cookie prompt or access error.
Check that the canonical URL does not redirect through several addresses or point to a different page.
Submit the URL to Meta's Sharing Debugger and request a new scrape after deploying the change.

Frameworks that render metadata only in the browser can confuse crawlers. In Next.js, server-render metadata through the Metadata API or document head. In a CMS, clear the page cache and any SEO-plugin cache after updating the tags.

If the warning remains

Make sure you changed the production page, not only a local preview.
Confirm the new tag is inside <head> and not printed as escaped text in the body.
Check for duplicate fb:app_id tags with different values.
Confirm the App ID belongs to the correct Meta app and has not been deleted.
Scrape the exact canonical HTTPS URL again; http, https, www, and non-www versions can have separate cached results.
If the preview is otherwise correct and you do not use a Meta app, document the warning instead of inserting false ownership metadata.

Treat fb:app_id as an ownership and integration setting, not a magic preview repair. Correct Open Graph content, crawlable server HTML, a reachable image, and a stable canonical URL are the parts that most directly determine what a sharing crawler can understand.

Frequently Asked Questions

Is fb:app_id required for every website?

No. The Open Graph protocol's four basic properties are og:title, og:type, og:image, and og:url. A Meta tool may still warn about fb:app_id because it connects a page to a Meta app, but the warning is not always the reason a link preview is broken.

Can I copy another website's Facebook App ID?

No. Use only an App ID for a Meta app that you or your organization controls. Borrowing an ID can create ownership, analytics, and maintenance problems.

Where does the fb:app_id tag go?

Place a meta tag with property set to fb:app_id inside the document head, and set its content to your own numeric Meta App ID.

Why does Facebook still show the old warning after I changed the page?

Meta may be using cached metadata. Confirm the tag exists in the server-rendered page source, then use the Sharing Debugger to scrape the URL again.