Open Graph OG Tags must be within the sourcecode!
There are several ways to serve an html containing open graph
tags ans solve your issue:
- Serverside rendering with angular universal
- use an proxy rendering your page
- overwriting index.html on the fly replacing og tags
- serving static html pages (not sure if this is supported by angular)
I guess you already use something like ngx-meta to add og tags?
Angular Universal – Server Side Rendering with meta tags in Angular 2/3/4/5
I guess server-side rendering is the most appropriate way to solve your issue. For this you can host a node server or use eg. AWS Lambda. The disadvantage with this, your app has to be actively hosted and can not be served statically anymore. Anyways this seems to be the best way since it also is improves SEO. Angular Universal is the term to search for:
- Angular Universal
- Angular Universal Starter Boilerplate
- Angular Universal PWA with serverside rendering serverless with aws lambda boilerplate
Angular Universal Prerendering on build
You can also prerender specific routes on the build process and serve angular as a static app with multiple prerendered index.html files. If you only have few static routes this works perfectly fine. Thinking of more generic routes with dynamic parts, this is not the solution. Go for server side rendering. The angular universal boilerplate also contains an example for this. See prerender.ts
Prerendering Angular with a proxy to provide OG Tags
If you like to avoid implementing serverside / prerendering during the build process (setting up angular universal sometimes is a pain for not good structured apps.) you can try to use a proxy service prerendering you page. Take a look at eg. prerender.io.
Redirect all requests to an script which overwrites the og:tags. Eg. Using PHP and .htaccess to overwrite og tags this is possible with modern environments too. Eg. you could use cloudfront / api gateway and a lambda function. Have not seen an example for this though.
Facebook Cache and Open Graph Debugging
Be aware that caches may still have cached the open graph information from their first crawl. Ensure your source code is the lastest and all caches, reverse proxies like nginxx, cloudfront are cleared.
Use Facebook Debugger to debug open graph caches and clear facebook opengraph cache