When Keynote navigation links fail in an exported PDF, verify the slide destinations first, export a simple test copy, then compare the same file in two viewers. This sequence helps you locate the failure before rebuilding your navigation.

This guide covers clickable buttons and text intended to jump between pages in a PDF made with Keynote on Mac. Apple documents how to create slide links and export PDFs, but its current export instructions do not promise preservation of every navigation behavior. The checks below distinguish documented controls from diagnostic suggestions.

What does Apple document—and where are the limits?

Keynote supports links on text and various objects, including shapes and groups. A link can target another slide. Apple’s current instructions do not support a blanket claim that grouped objects cannot have links. They also do not establish that every supported source object exports identically to PDF. Link to a webpage, email, phone number, or slide in Keynote on Mac.

Apple describes PDF export as putting each slide on its own PDF page, with options that can change the output. Its documented PDF settings contain no “preserve hyperlinks” or “include navigation controls” switch. These instructions therefore provide no such setting to enable as a repair. That documentation gap is not proof that all slide links are unsupported in PDFs. Export to PowerPoint or another file format in Keynote on Mac.

Also separate a clickable destination from slideshow playback. In Keynote, Normal and Links Only are presentation types; Links Only advances through link clicks. Apple documents them as slideshow navigation settings, not PDF export settings. Changing this option is useful when testing the presentation, but it is not a documented fix for exported PDF links. Choose how to navigate your presentation on Mac.

Check the failing link inside Keynote

Start with one button that fails consistently. Record its starting slide, visible label, and intended destination heading. For example: “Contents → Blue Shapes.” Identifying the destination by content will make the later PDF check clearer than relying only on page numbers.

To inspect an existing link, click its linked text or the link button beside the object. Check the destination in the link editor. To create a replacement, Control-click the intended object or selected text, choose Add Link > Slide, and specify the destination. Click Go to Slide to verify it. Apple documents these controls in its Keynote link instructions.

If Go to Slide reaches the wrong content, correct the destination before exporting again. If no link is attached to the intended text or object, create one explicitly. A label such as “Contents” describes a destination to the reader; it does not establish which destination the link actually uses.

Next, test the button during slideshow playback. Apple specifies Normal or Links Only for interactive navigation through linked objects. Select the starting slide and click Play. If using Links Only, give every slide an onward or return link so the presentation has no dead ends. Add linked objects to make your presentation interactive in Keynote on Mac.

Treat these as two separate observations: whether the editor resolves the destination, and whether the visible button works during playback. If either fails, continue repairing the source presentation. A successful source test is the prerequisite for investigating export behavior.

Export a controlled PDF for comparison

Choose File > Export To > PDF. For this diagnostic copy, leave Print each stage of builds off and include skipped slides if any are intended destinations. Apple explains that exporting each build stage creates additional pages, and that skipped slides have an inclusion option. Save the result with a distinct test filename. Export to PowerPoint or another file format in Keynote on Mac.

These choices simplify the comparison; they are not documented link-repair switches. First check that the destination content actually appears in the exported file. An absent destination and an unresponsive clickable area are different problems.

Use the direct export route for this baseline even if the failing file came from printing. Apple also documents print options, but does not state on this page that printing always removes links or that direct export always preserves them. Keeping one export route throughout the test avoids changing another variable.

Open the newly exported PDF in Preview, which Apple identifies as an application for opening these files. Click the suspect button and check the destination heading. Then open the same PDF file in another available PDF viewer and repeat the click. Do not re-export between viewer tests.

The following table is a diagnostic aid derived from those comparisons, not a list of confirmed Keynote bugs:

Test result What it suggests Next action
The destination is wrong inside Keynote The source link needs correction Fix it and verify again before export
The destination content is absent from the PDF The output lacks the intended target Recheck skipped-slide inclusion and the exported content
The same PDF link works in one viewer only Viewer behavior is a likely factor Check the intended viewer’s own link instructions
The source works, but the PDF fails in both viewers Export or object-specific behavior needs isolation Try the minimal test below
A minimal test works, but the original button fails The failure may depend on that button or document Simplify one affected button and compare again

Isolate the problem with a three-slide test

Before changing dozens of buttons, create a small separate presentation using neutral sample content. This is a proposed diagnostic experiment, not a reported test result:

  1. Make three slides titled Contents, Blue Shapes, and Green Shapes.
  2. On Contents, add a plain text link to the specific Blue Shapes slide.
  3. Add a separate, visible shape linked to the specific Green Shapes slide.
  4. On both destination slides, add a return link to Contents.
  5. Verify each destination in Keynote, test playback, then export with the same baseline settings.
  6. Test all four links in both PDF viewers.

This separates basic slide-to-slide navigation from the complexity of the original design. Use explicit destination slides for this experiment so the expected result is unambiguous. Test any relative navigation options used in the original presentation separately afterward.

If the plain text link works but a complex original button does not, try replacing just that button with a simple visible shape carrying the same destination. If both simple link types work, rebuild one original control at a time. These are isolation steps; Apple does not document them as guaranteed export fixes.

If the minimal presentation fails in both viewers despite working in Keynote, stop making broad design changes. Record your Keynote version, the export settings, the viewers used, and which sample links failed. Apple’s guide explains that Keynote > About Keynote shows the installed version. A small reproducible example makes a support request more precise. Keynote User Guide for Mac.

Would Pages bookmarks repair the Keynote PDF?

Pages has a different destination model. Its page-layout documents support links to pages, while word-processing documents support links to bookmarks. Those are Pages authoring controls; they are not additional destinations or repair commands in Keynote. Moving the task into Pages would mean authoring navigation in another document rather than diagnosing the existing slide links. Link to a webpage, email, phone number, or page in Pages on Mac.

Pages also limits bookmarks to body text in word-processing documents. Text inside a text box or shape cannot serve as a bookmark target under those instructions. This matters if a proposed workaround involves recreating slide-like layouts from text boxes: the documented bookmark workflow does not apply to that text. Add bookmarks and link to them in Pages on Mac.

Choose a fallback that preserves the reader’s task

If the reader needs the interactive slideshow itself, keep the presentation in Keynote and use its documented Normal or Links Only playback. That gives you a supported environment for the slide navigation you verified. It does not produce the requested PDF, so use it only when the delivery format can change.

If the deliverable must remain a PDF and source-level troubleshooting does not resolve it, a PDF editor with documented internal-link tools offers a separate repair path. Adobe documents creating a link area and assigning Go to a page view in Acrobat. With those editing tools available, open the PDF, select Edit, then under Add Content choose More > Link > Add or edit a link. Draw the clickable rectangle, select Go to a page view, and follow the destination prompts. Add links to PDFs.

Make PDF-level repairs on a copy after settling the page order. Keep a short record of repaired controls so a later Keynote export can be checked against it. For personal navigation in Preview, Apple also documents Tools > Add Bookmark, followed by View > Bookmarks; this creates sidebar navigation rather than repairing a button on the page. Bookmark PDF pages in Preview on Mac.

Finish by testing the exact PDF you intend to deliver: each contents link, each return button, and any alternative path through the document. Verify destination headings as well as click responses. That gives you a concrete acceptance check for the exported file while keeping source repairs, export behavior, and viewer behavior distinguishable.

Sources