<- Go Back
Getting Started
Confirming and Removing RankFrame's Custom Code
See exactly what RankFrame writes to your project's Custom Code, and remove it whenever you want.
Last Updated on
Read Time
4 min read
Why RankFrame asks before writing
Two RankFrame features write into your project's Custom Code: the 404 tracking script and schema injection. Custom Code is project-wide, so anything added there affects every page. RankFrame now shows you exactly what it will write and waits for you to confirm.
What the confirmation shows
The exact code that will be written, in full, scrollable.
Where it goes: the end of the <head> section for schema, the end of the <body> tag for the 404 script.
Whether this is a first install or a replacement. If a RankFrame block is already there, you see the currently installed code and the new code side by side.
A note that nothing else in your Custom Code is changed.
Nothing is written until you press Confirm and Inject. Cancel leaves your project untouched.
Removing what was added
Each feature has a Remove from Custom Code action with its own confirmation. It removes only the RankFrame block, marked by comment markers, and leaves everything else in your Custom Code exactly as it was.
Because RankFrame only ever writes inside its own markers, removal is a clean rollback rather than a rewrite of the field.
Publishing
Adding or removing Custom Code changes your project, not your live site. Publish your Framer site for the change to take effect.
If the buttons are greyed out
Writing Custom Code is a permission your Framer role may not have. When that is the case RankFrame disables the action and explains why, rather than letting you click and fail. Ask a project admin for edit access, or open RankFrame in a project where you can edit.
Frequently asked questions
What does RankFrame write to my Custom Code?
Two things: the 404 tracking script at the end of the body, and schema markup at the end of the head. Both are shown in full before anything is written.
Related to